Hi Johan,
I don't understand why you've interpreted the javadoc in that way. Here are
some things to consider:
Tapestry expects UTF-8. Eclipse handles UTF-8 just fine. Eclipse can be set to
default to UTF-8 for templates and properties:
Preferences > General > Content Types > Text > HTML > *.tml
Preferences > General > Content Types > Text > Java Properties File >
*.properties
On existing files, right-click and choose:
Properties > Resource > Text file encoding > Other > UTF-8
If you go down this path then all languages work without further thought, so
I'd sincerely recommend it.
You can see it working fine in all of JumpStart including the localization
examples.
Regards,
Geoff
On 12/02/2013, at 6:59 PM, Johan Stuyts wrote:
>> Have you encoded you file into utf8?
>
> Java properties files must never be encoded using UTF-8. The encoding for
> Java properties files is always the same: ISO-8859-1 with Unicode escapes.
> Your editor must convert any characters not in ISO-8859-1 to Unicode escapes.
>
> See the Javadoc of "Properties":
> <http://docs.oracle.com/javase/6/docs/api/java/util/Properties.html>.
>
> For Eclipse I recommend the following plug-in for editing properties files:
> <http://propedit.sourceforge.jp/index_en.html>.
>
> If the properties file is encoded as it should be and the characters are not
> displayed correctly, then some component is either:
> - Not reading the properties file properly, or
> - Doing incorrect/too many encodings or decodings of strings.
>
> --
> Regards, Johan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
