Re: Wicket Bulgarian translation (bg)
What version of Wicket are you using ?
You should have native2ascii encoded strings in the property file :
Required=\u00d0\u0178\u00d0\u00be\u00d0\u00bb\u00d0\u00b5\u00d1\u201a\u00d0\u00be
'${label}' \u00d0\u00b5
\u00d0\u00b7\u00d0\u00b0\u00d0\u00b4\u00d1\u0160\u00d0\u00bb\u00d0\u00b6\u00d0\u00b8\u00d1\u201a\u00d0\u00b5\u00d0\u00bb\u00d0\u00bd\u00d0\u00be.
2009/10/11 Girts Ziemelis girts.zieme...@gmail.com
Is anyone using wicket with bulgarian translations?
It seems, the standard wicket messages for bulgarian
Application_bg.properties are all messed up :(
Unfortunately I do not speak/write Bulgarian, but version of survey we are
running is also in BG and our Bulgarian colleagues are complaining about
standard error messages being messed up.
Site is in UTF-8 and many other non standard charset languages are working
fine (e.g. Russian, Latvian).
Strings in the wicket property file do not seem to contain proper Cyrillic
characters:
e.g: string for
Required=Полето '${label}' е задължително.
I do not believe is a proper cyrillic text.
Can anyone confirm the problem, before I submit the bug report?
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket Bulgarian translation (bg)
Wicket version is 4.1
Regarding encoding - I know - it is encoded in the properties file
-strings I posted are once the strings are decoded to UTF-8 -for IDE
(Netbeans, for example, does this automatically for *.properties files)
and for the web site (in UTF-8).
For example - ASCII escapes below - first letter \u00d0 is
http://www.fileformat.info/info/unicode/char/00d0/index.htm
which is not a letter from Cyrillic.
My understanding is that all cyrilic charset letters are in unicode
block \u04xx
http://czyborra.com/charsets/cyrillic.html
Are you using BG translation which works correctly?
Olivier Bourgeois wrote:
What version of Wicket are you using ?
You should have native2ascii encoded strings in the property file :
Required=\u00d0\u0178\u00d0\u00be\u00d0\u00bb\u00d0\u00b5\u00d1\u201a\u00d0\u00be
'${label}' \u00d0\u00b5
\u00d0\u00b7\u00d0\u00b0\u00d0\u00b4\u00d1\u0160\u00d0\u00bb\u00d0\u00b6\u00d0\u00b8\u00d1\u201a\u00d0\u00b5\u00d0\u00bb\u00d0\u00bd\u00d0\u00be.
2009/10/11 Girts Ziemelis girts.zieme...@gmail.com
Is anyone using wicket with bulgarian translations?
It seems, the standard wicket messages for bulgarian
Application_bg.properties are all messed up :(
Unfortunately I do not speak/write Bulgarian, but version of survey we are
running is also in BG and our Bulgarian colleagues are complaining about
standard error messages being messed up.
Site is in UTF-8 and many other non standard charset languages are working
fine (e.g. Russian, Latvian).
Strings in the wicket property file do not seem to contain proper Cyrillic
characters:
e.g: string for
Required=Полето '${label}' е задължително.
I do not believe is a proper cyrillic text.
Can anyone confirm the problem, before I submit the bug report?
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket Bulgarian translation (bg)
2009/10/12 Girts Ziemelis girts.zieme...@gmail.com Wicket version is 4.1 Regarding encoding - I know - it is encoded in the properties file -strings I posted are once the strings are decoded to UTF-8 -for IDE (Netbeans, for example, does this automatically for *.properties files) and for the web site (in UTF-8). For example - ASCII escapes below - first letter \u00d0 is http://www.fileformat.info/info/unicode/char/00d0/index.htm which is not a letter from Cyrillic. My understanding is that all cyrilic charset letters are in unicode block \u04xx http://czyborra.com/charsets/cyrillic.html Are you using BG translation which works correctly? I'm using BG translations for my app, but not the Wicket default ones, and I am using a mix of UTF-8 properties files and XML files. I just had a look with wicket 1.4.2 and the BG translations are broken : I think something went wrong with the native2ascii transformation. If you look at the history of the Wicket BG translation file, it used to be in UTF-8, but because Java properties does not hold UTF-8 it has been encoded in ASCII. Now that Wicket 1.4.x can work with XML properties. I think this file should be in XML, like RU file is today.
Re: Wicket Bulgarian translation (bg)
Olivier Bourgeois wrote: I'm using BG translations for my app, but not the Wicket default ones, and I am using a mix of UTF-8 properties files and XML files. I just had a look with wicket 1.4.2 and the BG translations are broken : I think something went wrong with the native2ascii transformation. If you look at the history of the Wicket BG translation file, it used to be in UTF-8, but because Java properties does not hold UTF-8 it has been encoded in ASCII. Now that Wicket 1.4.x can work with XML properties. I think this file should be in XML, like RU file is today. Yes - our BG translations from our property files also work fine - it is just the wicket standard messages. Ok, I will try to get the old translations back and encode them properly. It seems they are wrong since may 2006 :( Or is it really preferred to store them in XML? Currently russian is the only one in XML.
Re: Wicket Bulgarian translation (bg)
The advantage of UTF-8 vs ASCII is that the translators can directly read/write the property files without transcoding them, so I think it's better to go with XML (and less risky). But I don't know what the Wicket dev team prefer for Wicket default property files. 2009/10/12 Girts Ziemelis girts.zieme...@gmail.com Olivier Bourgeois wrote: I'm using BG translations for my app, but not the Wicket default ones, and I am using a mix of UTF-8 properties files and XML files. I just had a look with wicket 1.4.2 and the BG translations are broken : I think something went wrong with the native2ascii transformation. If you look at the history of the Wicket BG translation file, it used to be in UTF-8, but because Java properties does not hold UTF-8 it has been encoded in ASCII. Now that Wicket 1.4.x can work with XML properties. I think this file should be in XML, like RU file is today. Yes - our BG translations from our property files also work fine - it is just the wicket standard messages. Ok, I will try to get the old translations back and encode them properly. It seems they are wrong since may 2006 :( Or is it really preferred to store them in XML? Currently russian is the only one in XML.
Re: Wicket Bulgarian translation (bg)
we are fine with .properties or .properties.xml. its all good. -igor On Mon, Oct 12, 2009 at 8:25 AM, Olivier Bourgeois olivier.bourgeois@gmail.com wrote: The advantage of UTF-8 vs ASCII is that the translators can directly read/write the property files without transcoding them, so I think it's better to go with XML (and less risky). But I don't know what the Wicket dev team prefer for Wicket default property files. 2009/10/12 Girts Ziemelis girts.zieme...@gmail.com Olivier Bourgeois wrote: I'm using BG translations for my app, but not the Wicket default ones, and I am using a mix of UTF-8 properties files and XML files. I just had a look with wicket 1.4.2 and the BG translations are broken : I think something went wrong with the native2ascii transformation. If you look at the history of the Wicket BG translation file, it used to be in UTF-8, but because Java properties does not hold UTF-8 it has been encoded in ASCII. Now that Wicket 1.4.x can work with XML properties. I think this file should be in XML, like RU file is today. Yes - our BG translations from our property files also work fine - it is just the wicket standard messages. Ok, I will try to get the old translations back and encode them properly. It seems they are wrong since may 2006 :( Or is it really preferred to store them in XML? Currently russian is the only one in XML. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket Bulgarian translation (bg)
Thanks - I added problem report WICKET-2518 https://issues.apache.org/jira/browse/WICKET-2518 Attached is a patch for Application_bg.properties file with properly encoded bg translations Igor Vaynberg wrote: we are fine with .properties or .properties.xml. its all good. -igor On Mon, Oct 12, 2009 at 8:25 AM, Olivier Bourgeois olivier.bourgeois@gmail.com wrote: The advantage of UTF-8 vs ASCII is that the translators can directly read/write the property files without transcoding them, so I think it's better to go with XML (and less risky). But I don't know what the Wicket dev team prefer for Wicket default property files. 2009/10/12 Girts Ziemelis girts.zieme...@gmail.com Olivier Bourgeois wrote: I'm using BG translations for my app, but not the Wicket default ones, and I am using a mix of UTF-8 properties files and XML files. I just had a look with wicket 1.4.2 and the BG translations are broken : I think something went wrong with the native2ascii transformation. If you look at the history of the Wicket BG translation file, it used to be in UTF-8, but because Java properties does not hold UTF-8 it has been encoded in ASCII. Now that Wicket 1.4.x can work with XML properties. I think this file should be in XML, like RU file is today. Yes - our BG translations from our property files also work fine - it is just the wicket standard messages. Ok, I will try to get the old translations back and encode them properly. It seems they are wrong since may 2006 :( Or is it really preferred to store them in XML? Currently russian is the only one in XML. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
