<i18n dev> RFR [jdk8u-dev]: Add pl localization to jar tool
michael.fang at oracle.com
Thu Mar 26 00:01:31 UTC 2015
Thank you for your reply.
User Interface translation for JRE and JDK are different. JDK "tools"
(ex: "javac", "native2ascii", "javadoc") are translated to ja and zh_CN
only (except "jar"). JRE resources are translated to 10 languages. These
languages are "supported" because we have linguistic resource to support
them if bugs are filed.
On 2015年03月24日 15:14, Jacob Wisor wrote:
> Hello Michael,
> Am 24.03.2015 um 18:31 schrieb Michael Fang:
>> Hi Jabob,
>> Thank you very much for contributing to the translation of
>> native2ascii tool and
>> jar tool.
>> The information displayed on http://openjdk.java.net/groups/i18n was
>> prior to JDK8. Due to Makefile updates, the localization instruction
>> does not
>> work anymore. We need to fix this page ASAP.
> Yeah, I have noticed this too, right after I had localized
> sun/tools/javac/resources/javac.properties only to find out that it is
> used by the outdated compiler only. I should have started with
> com/sun/tools/javac/resources/javac.properties. But anyway, now I have
> localized them both.
>> Currently, we are not able to support additional language translation
>> in OpenJDK
>> bundles without also including them in Oracle JDK bundles.
> Why is this a problem? Everybody is free to use OpenJDK in their
> products, including Oracle. And, if you are referring to the fact that
> additional localizations may possibly require additional customer
> support then I will have to disappoint you: Various currently
> "supported" localizations are incomplete in various places, tools, and
> components, eg. like de or sv. So, "requiring additional support" is
> actually an invalid argument.
> Another possibility for Oracle - if Oracle /really/ wants to waste
> existing language support - is to foster a build infrastructure that
> drops localization support for certain locales at build time. It is
> odd and perhaps inconvenient but possible.
>> To add additional localization to your environment, you could create
>> a jar file with translated
>> resource files and place the jar file under <java_home>/lib/ext
>> directory (works
>> up to JDK8).
> Yes, I know. But, this would be rather tedious for many people to
> install. Besides, this/these multi-language JAR file(s) would have to
> be hosted somewhere for people to find and download easily. Including
> all localizations into OpenJDK and then perhaps excluding them for
> Oracle JDK is probably the best way to go.
>> On 2015年03月09日 13:10, Jacob Wisor wrote:
>>> Hello there!
>>> I have added pl localization to the JAR tool. However, I did not
>>> find the
>>> make/common/Defs.gmk file which is referenced here:
>>> Please review this patch. More tools are coming! ;-)
More information about the i18n-dev