Mission accomplished. I used the method with *.utf8.properties.
I'm sure the properties in xml files had also worked.
Wicket localization is great.
Thanks for helping.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/How-to-localize-options-in-drop-down-tp4661751p
,
Paul Bors
-Original Message-
From: Vit Rozkovec [mailto:rozkovec...@email.cz]
Sent: Wednesday, October 09, 2013 4:49 AM
To: users@wicket.apache.org
Subject: Re: How to localize options in drop down.
If you would be using Eclipse IDE you can use this:
http://propedit.sourceforge.jp/index_en.html
Well, use *.utf8.properties and then you can just use UTF-8 encoding:
property.date=Fällig ab
Sven
On 10/09/2013 10:45 AM, cosmindumy wrote:
Yes,
Now they are unicode. Something like property.date=F\u00E4llig ab.
But I want to use native characters in propery file as is easier to handle.
If you would be using Eclipse IDE you can use this:
http://propedit.sourceforge.jp/index_en.html
On 9.10.2013 10:45, cosmindumy wrote:
Yes,
Now they are unicode. Something like property.date=F\u00E4llig ab.
But I want to use native characters in propery file as is easier to handle.
--
View t
Yes,
Now they are unicode. Something like property.date=F\u00E4llig ab.
But I want to use native characters in propery file as is easier to handle.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/How-to-localize-options-in-drop-down-tp4661751p4661763.html
Sent from t
Do you use unicode escapes or how do you enter unicode characters?
Sven
On 10/09/2013 10:23 AM, cosmindumy wrote:
Hello,
Thanks for answering.
They are in *.properties.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/How-to-localize-options-in-drop-down-tp466175
Hello,
Thanks for answering.
They are in *.properties.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/How-to-localize-options-in-drop-down-tp4661751p4661761.html
Sent from the Users forum mailing list archive at Nabble.com.
Hi,
in which files do you keep your localized strings? *.properties,
*.properties.xml or *.utf8.properties?
Sven
On 10/08/2013 05:49 PM, cosmindumy wrote:
Solved the localization problem.
I didn't know wicket convention about localization in choices.
There is still the problem with utf-8.
Th
Solved the localization problem.
I didn't know wicket convention about localization in choices.
There is still the problem with utf-8.
Thanks.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/How-to-localize-options-in-drop-down-tp4661751p4661753.html
Sent from the