8385927: JDK 27 RDP1 L10n resource files update#31486
Conversation
| validity.number.of.days=有效天数 | ||
| Serial.ID.of.cert.to.revoke=要撤销的证书的序列 ID | ||
| # keytool: Running part | ||
| keytool.error.=keytool 错误：\u0020 |
There was a problem hiding this comment.
This change and similar ones are expected. Trailing white space is no longer required when the last char is a full-width colon which zh_CN files commonly do.
|
👋 Welcome back jlu! A progress list of the required criteria for merging this PR into |
|
@justin-curtis-lu This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be: You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 4 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
|
@justin-curtis-lu The following labels will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing lists. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
|
|
||
| compiler.misc.incompatible.arg.types.in.lambda=ラムダ式のパラメータ型は不適合です | ||
| # 0: list of type or message segment, 1: list of type or message segment | ||
| compiler.misc.incompatible.arg.types.in.lambda=ラムダ式のパラメータ型は不適合です\n期待値: {0}\n検出値: {1} |
There was a problem hiding this comment.
Those extra spaces between "検出値:\u0020" and "{1}" seems unnecessary. Original English resource has these spaces to align the placeholders, but not needed for Japanese
There was a problem hiding this comment.
Fixed. Curious as to why the de translation for this key came back without the extra spaces, but the ja one did. Assuming zh_CN operated differently given its full width colon.
There was a problem hiding this comment.
I guess de/zh_CN translators were aware of the original alignment. De translator simply removed them, zh_CN translator removed them which happened to align placeholders. Ja translator simply copied them over.
| # {0} = path of jimage file, {1} = underlying error message | ||
| err.invalid.jimage={0}を開けません: {1} | ||
| # More specific alternative for cases of version mismatch | ||
| err.wrong.version={0}を開けません: ファイルとツールのバージョンが一致していません\njimageファイルに関連付けられたJDKには''<JAVA_HOME>/bin/jimage''を使用してください:\n{1} |
There was a problem hiding this comment.
I believe this translation is not accurate. The second sentence should be something along the lines of:
jimageファイルに関連付けられたJDKの''<JAVA_HOME>/bin/jimage''を使用してください:\n{1}
…bda in compiler_ja.properties
2 participants
Localization updates for JDK 27 RDP1.
For easier review, you can also view the changes side-by-side with the corresponding English changes here:
https://cr.openjdk.org/~jlu/output/. Note that translations come from upstream as usual, so any modifications made in this PR will also need to be applied upstream. While most changes are the result of updates to the corresponding English values, it is not unusual to also see some updates to existing translations.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/31486/head:pull/31486$ git checkout pull/31486Update a local copy of the PR:
$ git checkout pull/31486$ git pull https://git.openjdk.org/jdk.git pull/31486/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 31486View PR using the GUI difftool:
$ git pr show -t 31486Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/31486.diff
Using Webrev
Link to Webrev Comment