Ok, I can only say that it works for properties in JVM 1.5

Proper way offcourse is to use native2ascii

On 15/07/07, Michael Grundvig <[EMAIL PROTECTED]> wrote:
The -Dfile.encoding option doesn't always work properly, it's documented on
the Java site here:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4163515

Basically, it seems to work on some VMs but you really need to just make
sure the file matches the encoding of the OS or specify an encoding on the
stream directly. This is why pretty much everything lets you pass in an
encoding when dealing with bytes.

Mike


----- Original Message -----
From: "Renat Zubairov" <[EMAIL PROTECTED]>
To: "Tapestry users" <users@tapestry.apache.org>
Sent: Sunday, July 15, 2007 10:09 AM
Subject: Re: properties file does not support UTF8


> Properties files do support UTF-8, you just need to encode them proper
>
> See
>
> native2ascii util from JDK or set your default Java file encoding to
> UTF-8 using "-Dfile.encoding=utf8"
>
> Renat
>
> On 14/07/07, sun58224 <[EMAIL PROTECTED]> wrote:
>> 1.properties file does not support UTF8.
>> 2.Sort BeanForms can not be changed.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
> --
> Best regards,
> Renat Zubairov
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




--
Best regards,
Renat Zubairov

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to