Hello List, I'd like to discuss, how to handle properties files for geoserver.
In the past, Christian (http://www.mail-archive.com/geoserver-devel@lists.sourceforge.net/msg12071.html) already started the discussion about UTF8 vs. some other encodings a while ago. While I has been working on German translations in the last weeks and month I was in close dialogue with translation specialists from transifex.net. Summarizing this communication: - standard expected encoding for java properties files readers and writers is ISO 8859-1 (http://en.wikipedia.org/wiki/ISO/IEC_8859-1), see see javadoc 1.4 (http://docs.oracle.com/javase/1.4.2/docs/api/java/util/Properties.html) and 6 (http://docs.oracle.com/javase/6/docs/api/java/util/Properties.html) - "Characters that cannot be directly represented in this encoding can be written using Unicode escapes" (\uXXXX) I suggest to switch over to the ISO Standard encoding for properties files. I guess eclipse also uses per default ISO 8559-1, if the developer uses the Action "externalize Strings". IMHU it would be easier to work with third-party tools like transifex, that explicit working on the Java standards. BTW, if all characters are encoded by \uXXXX sequences, everything would be fine in the future. Thanks for feedback and suggestions -Frank ------------------------------------------------------------------------------ Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
