<i18n dev> native2ascii be removed from JDK?

Erik Joelsson erik.joelsson at oracle.com
Wed Apr 8 08:32:24 UTC 2015

Note that the JDK build itself uses native2ascii for the man pages. I 
have no idea why or if this is actually necessary. Here is the code:

   define install-ja-manpage
         $(MKDIR) -p $(@D)
         $(CAT) $< \
             | $(NATIVE2ASCII) -encoding eucJP \
             | $(SED) 's/@@VERSION@@/$(THIS_JDK_VERSION)/g' \
             | $(NATIVE2ASCII) -reverse -encoding $1 \
             > $@


On 2015-03-30 23:37, Mandy Chung wrote:
> There are several existing ways to do native to ascii conversion.  For 
> example, IDEs like NetBeans and IntelliJ support the transparent 
> native-to-ascii conversion. There is also maven native 2 ascii plugin.
> JEP 226 proposes to support UTF Properties file that will address the 
> original motivation of creating the native2ascii tool.
> While native2ascii used to be a convenient tool for some developers to 
> use, it may be time to remove it in JDK 9 and developers can use IDEs 
> and Maven plugin and other build tools.
> Any thought?
> Mandy

More information about the i18n-dev mailing list