Are you sure tapestry/jetty has anything to do with it? Can you write a straight java (no webapp/jetty) unit test that loads the file?
On Thu, May 26, 2011 at 1:32 PM, atcach <atc...@gmail.com> wrote: > Furthermore, if I open the .xml from an hex editor, I only see the < sign, > not the BOM for any encoding. > 00000000: 3c 3f 78 6d 6c 20 76 65 72 73 69 6f 6e 3d 22 31 <?xml > version="1 > 00000010: 2e 30 22 20 65 6e 63 6f 64 69 6e 67 3d 22 55 54 .0" > encoding="UT > 00000020: 46 2d 38 22 3f 3e 0a 3c 63 6f 6e 74 65 6e 74 20 > F-8"?>.<content > > Which is quite right, isn't it ? > As: > UTF-8 BOM: ef bb bf > UTF-16BE BOM: fe ff > UTF-16LE BOM: ff fe > UTF-32BE BOM: 00 00 fe ff > UTF-32LE BOM: ff fe 00 00 > > Regards > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/T5-Locale-problem-tp4428763p4429973.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
