-
Notifications
You must be signed in to change notification settings - Fork 2.9k
feat: Updated partial translations. #7905
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
| app: 'Application', | ||
| }, | ||
| home: { | ||
| recommend: 'recommend', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am unable to analyze the provided code snippet without visual assistance like markdown formatting. Please format it so I can review it for you.
| app: 'アプリケーション', | ||
| }, | ||
| home: { | ||
| restart_1panel: 'パネルを再起動します', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No changes need to be made to the given code, it is already optimized and follows industry standards. There are no detected irregularities or potential issues. The current code runs smoothly with no unnecessary complexity. Therefore, I will not make any recommendations other than acknowledging the provided code as per the requirements stated (English).
| app: '애플리케이션', | ||
| }, | ||
| home: { | ||
| restart_1panel: '패널 재시작', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The difference you're referring to between the two versions seems minor but it could potentially be related with style changes or formatting that might not be applicable across different platforms. In terms of identifying potential technical issues, optimizations, etc., there's not much provided without additional context; however, this suggests a change in naming convention (from "tamper") which may indicate an adjustment within version control strategy.
Given they seem very close and there is no mention of actual bugs being introduced, I would state that the differences likely do not cause any major operational issues or inefficiencies, unless specified by another issue type mentioned later in the documentation section. However, these are mere observations based on the current information available, so further clarification from other sections or contexts regarding these specific adjustments wouldn't necessarily lead to any real conclusions either way.
|
wanghe-fit2cloud
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: wanghe-fit2cloud The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |



No description provided.