Ah, this is the problem. How could you force the translators not to use
notepad?
Billy Ng
- Original Message -
From: <[EMAIL PROTECTED]>
To:
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, October 17, 2007 4:03 PM
Subject: RE: UTF-8 Properties File
Hi,
Are you sure that
ly Ng [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 17, 2007 3:26 PM
To: Tomcat Users List
Subject: Re: UTF-8 Properties File
Don't know why It happens to me. If you google "native2ascii BOM",
you
will see what other people were complaining.
Billy Ng
- Original
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Billy,
(Note that this isn't a Tomcat problem; it's a Java problem.)
Billy Ng wrote:
> Don't know why? It happens to me. If you google "native2ascii BOM",
> you will see what other people were complaining.
They are complaining that native2ascii is
October 17, 2007 1:26 PM
Subject: Re: UTF-8 Properties File
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Billy,
Billy Ng wrote:
This is the major problem for the people to localize context. \u
unicode format is not readable to them.
That's why most people use native2ascii as part o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
Konstantin Kolinko wrote:
> You may try some tools to edit those files.
I am a native English speaker, and we use Attesoro
(http://attesoro.org/) to create localized properties files. It allows
you to use natural text, but saves to ISO-8859-1 tr
> unicode format is not readable to them.
>
> The native2ascii will add the BOM to the beginning to fail ResourceBundle.
>
> Billy Ng
>
> - Original Message -
> From: "Tim Funk" <[EMAIL PROTECTED]>
> To: "Tomcat Users List"
> Sent: Wednesd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Billy,
Billy Ng wrote:
> This is the major problem for the people to localize context. \u
> unicode format is not readable to them.
That's why most people use native2ascii as part of their deployment
procedure, and don't bother developers with t
cat Users List"
Sent: Wednesday, October 17, 2007 3:40 AM
Subject: Re: UTF-8 Properties File
There is no such thing as UTF-8 properties files. Tomcat follows the same
rules as java when reading properties files.
Properties file must be ISO8859-1 and if you have characters outside of
tha
> Besides using native2ascii, would someone please recommend me how to make
> tocmat to work with UTF-8 properties files, thanks!
After using native2ascii on your property files, put the following tag in your
JSP files:
<%@ page contentType="text/html;charset=UTF-8" language="java" %>
There is no such thing as UTF-8 properties files. Tomcat follows the
same rules as java when reading properties files.
Properties file must be ISO8859-1 and if you have characters outside of
that character set - then you use native2ascii to encode those other
characters.
-Tim
Billy Ng wrote
10 matches
Mail list logo