Re: UTF-8/BOM Problem Again

2007-01-11 Thread Jose Cornado
It works now! It was an intermitent failure so it was hard to track. On 1/11/07, Jose Cornado <[EMAIL PROTECTED]> wrote: Before hand, I ask your forgiveness if this issue has been raised before :-] But I have been chasin my tail for a while. This is the hex dump of prolog: 3c 3f 78 6d 6c 20

Re: UTF-8/BOM Problem Again

2007-01-11 Thread Jose Cornado
I have even tried the following new OutputStreamWriter(new FileOutputStream(File), "UTF-16"); ... InputSourceTempIS= new InputSource(File.toURI().toString()); TempIS.setEncoding("UTF-16"); AParser.parse(TempIS, Handler); And changed the prolog to reflect UTF-16. The hex editor correctly

Re: UTF-8/BOM Problem Again

2007-01-11 Thread Bullotta, Rick
To: j-users@xerces.apache.org Sent: Thu Jan 11 13:15:56 2007 Subject: UTF-8/BOM Problem Again Before hand, I ask your forgiveness if this issue has been raised before :-] But I have been chasin my tail for a while. This is the hex dump of prolog: 3c 3f 78 6d 6c 20 = "http://www.efekctive.

UTF-8/BOM Problem Again

2007-01-11 Thread Jose Cornado
Before hand, I ask your forgiveness if this issue has been raised before :-] But I have been chasin my tail for a while. This is the hex dump of prolog: 3c 3f 78 6d 6c 20 = "http://www.efekctive.com blog: http://www.efekctive.com/blogging -- Everything has been said befor