- Original Message -
From: Mike Pogue <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, January 28, 2000 9:23 PM
Subject: Re: xml encodings, java
Hello!
And thank you for your perfect answer!
> I'm not sure how Cocoon works, but let me summarize how encodin
Valley
[EMAIL PROTECTED]
Tim Bray <[EMAIL PROTECTED]> on 01/28/2000 11:22:57 AM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: Re: xml encodings, java
At 11:28 AM 1/28/00 -0700, [EMAIL PROTECTED] wrote:
>Slight correction... The BOM is required for UTF-16 on
At 11:28 AM 1/28/00 -0700, [EMAIL PROTECTED] wrote:
>Slight correction... The BOM is required for UTF-16 only if the XMLDecl
>line (figure it out from that (though a BOM can also still be present.)
Well, only maybe.
Section 4.3.3 says; "Entities encoded in UTF-16 must begin with the Byte
Order
Slight correction... The BOM is required for UTF-16 only if the XMLDecl
line ( on 01/28/2000 09:23:18 AM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: Re: xml encodings, java
I'm not sure how Cocoon works, but let me summarize how encodings work
in general.
Message -
> From: Mike Pogue <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, January 28, 2000 8:33 PM
> Subject: Re: xml encodings, java
>
> > The code you have below is a clever workaround, but ultimately, you want
> > to use a JVM that has the
- Original Message -
From: Mike Pogue <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, January 28, 2000 8:33 PM
Subject: Re: xml encodings, java
> The code you have below is a clever workaround, but ultimately, you want
> to use a JVM that has the encodin
Which encodings are available to you depends HEAVILY on the encoding
support in the underlying JVM. In your case: Blackdown.
Note that Sun does NOT require JVM's to support the same encodings that
the Sun JVM does.
And, the Xerces-J parser does NOT do it's own encoding support -- it
uses whatever
