Hi, Thank you for your feedback. I found a couple of messages not translated at all. I need to put some more effort on this (I have to check the context of these error messages) so the translation will be delayed. Hopefully, I'll have it done by the weekend.
:) maanantai, 27. tammikuuta 2014 19.14.11 UTC+1 Thomas Mueller kirjoitti: > > Hi, > > Fixed translations are very welcome! > > > What encoding should I use? The file seems to be saved in ANSI. > > You should use UTF-8. The file is saved in UTF-8 encoding. The Polish > translation currently doesn't use any characters beyond character code 127 > I guess, and UTF-8 and ANSI are the same for those. > > The files _messages_*.prop are not properties (java.util.Properties) files > (please note the suffix is ".prop" and not ".properties"). The files > _messages_*.prop are stored in UTF-8 encoding. See for example the Japanese > translation at > https://code.google.com/p/h2database/source/browse/trunk/h2/src/main/org/h2/res/_messages_ja.prop. > > Regards, > Thomas > > > > > > > On Mon, Jan 27, 2014 at 9:18 AM, pwagland <[email protected] <javascript:> > > wrote: > >> Hi WJ, >> >> Almost unbelievably, the default encoding for properties files is ISO >> 8859-1. From the >> JavaDoc<http://docs.oracle.com/javase/7/docs/api/java/util/Properties.html> >> : >> >> The >> load(Reader)<http://docs.oracle.com/javase/7/docs/api/java/util/Properties.html#load(java.io.Reader)> >> / store(Writer, >> String)<http://docs.oracle.com/javase/7/docs/api/java/util/Properties.html#store(java.io.Writer,%20java.lang.String)> >> methods >> load and store properties from and to a character based stream in a simple >> line-oriented format specified below. >> Theload(InputStream)<http://docs.oracle.com/javase/7/docs/api/java/util/Properties.html#load(java.io.InputStream)> >> / store(OutputStream, >> String)<http://docs.oracle.com/javase/7/docs/api/java/util/Properties.html#store(java.io.OutputStream,%20java.lang.String)> >> methods >> work the same way as the load(Reader)/store(Writer, String) pair, except >> the input/output stream is encoded in ISO 8859-1 character encoding. >> Characters that cannot be directly represented in this encoding can be >> written using Unicode escapes as defined in section 3.3 of The Java™ >> Language Specification; 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. >> >> >> So, I would say, save the file in its current encoding, but do the ę as >> \u0119. >> >> Hope that helps! >> >> Cheers, >> Paul >> >> >> On Sunday, January 26, 2014 1:39:11 PM UTC+1, Wojtek Jurczyk wrote: >>> >>> Hello everyone! >>> >>> I found a couple of misspelled words in Polish translation and I would >>> like to fix them. After I found the translation file a simple question came >>> to my mind. What encoding should I use? The file seems to be saved in ANSI. >>> Obviously, that makes the translation easy to print out in every system but >>> on the other hand some "special" letter are missing ("a" instead of "ą" >>> etc). Using the simplest encoding sounds reasonable but having polish >>> letters in the translation sounds nice. Should I correct the typos I've >>> found and add polish letters and save the file in UTF8 or just the typos >>> and save the file as it is? >>> >>> Regards, >>> WJ >>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "H2 Database" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To post to this group, send email to [email protected]<javascript:> >> . >> Visit this group at http://groups.google.com/group/h2-database. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/groups/opt_out.
