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
Does it mean that the old-school (name-value, not xml) property files for
Tapestry now *have to be* encoded in UTF-8 rather than the standard Latin-1?
Kalle
On Fri, Aug 1, 2008 at 6:41 AM, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
> If you update again, you'll get the snapshot that reads pro
Yes !!!
Thank you :)
Howard Lewis Ship wrote:
>
> If you update again, you'll get the snapshot that reads properties
> files correctly (kind of an implicit native2ascii).
>
> On Fri, Aug 1, 2008 at 4:06 AM, Martin Papy <[EMAIL PROTECTED]>
> wrote:
>>
>> Hello everybody,
>>
>> I updated with t
If you update again, you'll get the snapshot that reads properties
files correctly (kind of an implicit native2ascii).
On Fri, Aug 1, 2008 at 4:06 AM, Martin Papy <[EMAIL PROTECTED]> wrote:
>
> Hello everybody,
>
> I updated with the last Snapshot. Has I understand, T5 now handles by
> default eve
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
