-----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 not removing the BOM mark from their input files, not that the BOM is being added to the output files. UTF-8-encoded files do not need a BOM, but it is not strictly prohibited. In your case, you already have a BOM in your UTF-8 file. While it's regrettable that Sun won't fix the bug (actually, they have, and then they un-fixed it because it broke older code), you ought to be able to work around it. There are so many workarounds, I'm not sure where to start. Here are the ones I can immediately think of, in increasing-PITA-order: - - Use UTF-16 as your source encoding instead of UTF-8. - - Add a comment or blank line at the top of your properties files. All my props files have a comment and CVS info at the top, which is why I've never noticed. - - Do you use native2ascii in your deployment, or do you hand-transcode these files when necessary? I ask because it would be pretty easy to chop-off the BOM from the file before running it through native2ascii if you were doing it as part of an automated deployment. - - Another strategy would be to write your own native2ascii, which shouldn't be too difficult to do; write it with the BOM-sensitivity in mind. You could even replace native2ascii on your system. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHFpQ+9CaO5/Lv0PARAl7cAJ9mL2WEIzw3z/Z7OewZEDjGfqrZ8wCeL5Ih J9E2eGX/laAtic3ZuI56kE4= =8ZdG -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
