Community
Participate
Working Groups
As per Daniel's message on babel-dev: http://www-306.ibm.com/software/globalization/topics/dev_java/lesson1.jsp Keep in mind that property files must be written using Latin-1 and/or Unicode escape sequence characters. native2ascii, which comes with Java SDK, converts files which contain other character encodings into the format above. http://java.sun.com/javase/6/docs/api/java/util/Properties.html Characters that cannot be directly represented in this encoding [ISO 8859-1]can be written using Unicode escapes ; only a single 'u' character is allowed in an escape sequence. The native2ascii tool can be used to convert property files to and from other character encodings.
I've committed a fix for this. Looks like our jsons library can do this. I'm generating a test update site now. generate1.php > 1.12
Created attachment 91565 [details] Screenshot of preferences, Russian and Arabic This looks much better. I created a staging area update site for testing. Not all the language packs work as not all the files/strings are on the staging area, but Russian, Arabic and Spanish are known to work. http://build.eclipse.org/technology/babel/test-updates/ This fix will be live in the next code deployment.
Released > R_0_200803051327
Released > R_0_200804081317
