<i18n dev> [7u]: org.omg.PortableServer.AdapterActivator.java compile fails on French platform

Francis ANDRE francis.andre.kampbell at orange.fr
Mon Dec 2 20:03:37 PST 2013


Hi

Found a surprising issue when building the jdk7u on a French platform with this 
compile error

Z:\JDK\JDK7U-~2\build\windows-i586\corba\gensrc\org\omg\PortableServer\AdapterActivator.java:8: 
error: unmappable character for encoding ascii
* lundi 2 d?cembre 2013 19 h 22 CET
            ^

In effect, the header generated is

/**
* org/omg/PortableServer/AdapterActivator.java .
* Generated by the IDL-to-Java compiler (portable), version "3.2"
* from ../../../../src/share/classes/org/omg/PortableServer/poa.idl
* lundi 2 décembre 2013 19 h 22 CET
*/
  which contains the "é" character in the french month of december.

As the compiling command request an ASCII encoding, it fails as "é" is not ASCII.

make[5]: Entering directory 
`/cygdrive/Z/JDK/jdk7u-dev/corba/make/org/omg/PortableServer'
if [ -s 
Z:/JDK/JDK7U-~2/build/windows-i586/corba/tmp/org/org.omg.PortableServer/.classes.list 
] ; then \
   /usr/bin/cat 
Z:/JDK/JDK7U-~2/build/windows-i586/corba/tmp/org/org.omg.PortableServer/.classes.list; 
\
   C:/Progra~1/Java/jdk1.6.0_35/bin/java -XX:-PrintVMOptions 
-XX:+UnlockDiagnosticVMOptions -XX:-LogVMOutput -client -Xmx512m -Xms512m 
-XX:PermSize=32m -XX:MaxPermSize=160m 
"-Xbootclasspath/p:Z:/JDK/JDK7U-~2/build/WINDOW~1/LANGTO~1/dist/bootstrap/lib/javac.jar" 
-jar Z:/JDK/JDK7U-~2/build/WINDOW~1/LANGTO~1/dist/bootstrap/lib/javac.jar 
-XDignore.symbol.file=true -source 7 -target 7 *-encoding ascii *-classpath 
C:/Progra~1/Java/jdk1.6.0_35/lib/tools.jar  -Xprefer:source -sourcepath 
"Z:/JDK/JDK7U-~2/build/windows-i586/corba/gensrc;../../../../src/windows/classes;../../../../src/share/classes" 
-d Z:/JDK/JDK7U-~2/build/windows-i586/corba/classes 
@Z:/JDK/JDK7U-~2/build/windows-i586/corba/tmp/org/org.omg.PortableServer/.classes.list; 
\
fi


I would suggest to fix this issue by removing the "-encoding ascii" parameter 
since pao.idl should contains only ascii characters and is not subject to i18n 
problem (except for the idl-to-java translation time in the header comment).

Francis


More information about the i18n-dev mailing list