Thanks Jose for a confirmation. Yes, that's what I thought and the problem
is the same as described in
http://www.thoughtsabout.net/blog/archives/44.html. As long as this is
documented properly, it's probably ok, but may cause problems if somebody
tries to use existing property files in a jar o
Kalle,
I just made the test on my app, since I had a char encoding problem for
about a week with 5.0.14-SNAPSHOT, and had to fallbacl to 5.0.13. So
yes, accented chars in ISO-8859 properties files are not rendered
properly in the final HTML page. If you switch the coding of that
property file
onnexion
> >
> > The page is in UTF-8, the Content-Type is also declaring UTF-8...
> >
> > I tried various encoding for the properties file : UTF-8 w/wo BOM,
> > ISO-8859-1...
> >
> > Any help
gt;
>> test-msg=Déconnexion
>>
>> Html output :
>>
>> DÃ(c)connexion
>>
>> The page is in UTF-8, the Content-Type is also declaring UTF-8...
>>
>> I tried various encoding for the properties file : UTF-8 w/wo BOM,
>> ISO-8859-1...
>
..
>
> I tried various encoding for the properties file : UTF-8 w/wo BOM,
> ISO-8859-1...
>
> Any help ?
>
> Thanks !
> --
> View this message in context:
> http://www.nabble.com/T5-UTF-8-new-behaviour-in-T5.0.14-tp18772210p18772210.html
> Sent from the Tapestry - Us
Martin Papy wrote:
Hello everybody,
I updated with the last Snapshot. Has I understand, T5 now handles by
default everything in UTF-8. That is ok for me.
But how the properties files are handled ?
I updated all my properties files in UTF-8 Encoding but I get odd
characters...
Hum, that seem
encoding for the properties file : UTF-8 w/wo BOM,
ISO-8859-1...
Any help ?
Thanks !
--
View this message in context:
http://www.nabble.com/T5-UTF-8-new-behaviour-in-T5.0.14-tp18772210p18772210.html
Sent from the Tapestry - User mailing list archive at Nabble.com
