That's fine, I'm just saying avoid using java encodings.
Richard
Ole Husgaard wrote:
>
> Hi,
>
> Why not use UTF-8?
>
> After all, every xml processor is required to support
> this encoding, and the plain (7bit) ASCII subset of
> UTF-8, Cp1252 and ISO-8859-1 are the same so simply
> changing the encoding should not change anything for
> these characters. (But I wouldn't be surprised if
> "�berg" became "Vberg").
>
> See http://www.w3.org/TR/1998/REC-xml-19980210#charencoding
>
> Best Regards,
>
> Ole Husgaard.
>
> Richard Backhouse wrote:
> >
> > Just change the :
> >
> > <?xml version="1.0" encoding="Cp1252"?>
> >
> > to :
> >
> > <?xml version "1.0" encoding="ISO-8859-1"?>
> >
> > in any of your xml files that specify Cp1252
> >
> > Richard
> >
> > marc fleury wrote:
> > >
> > > ok so how do we change that Cp setting?
> > >
> > > marc
> > >
> > > |-----Original Message-----
> > > |From: [EMAIL PROTECTED]
> > > |[mailto:[EMAIL PROTECTED]]On Behalf Of Richard Backhouse
> > > |Sent: Friday, October 27, 2000 5:55 AM
> > > |To: jBoss Developer
> > > |Subject: [jBoss-Dev] Small thing I noticed
> > > |
> > > |
> > > |FYI
> > > |
> > > |I have noticed that the majority of xml file provided with jboss have
> > > |and encoding set to Cp1252. You may not know but this is only supported
> > > |by default by suns xml parser. If you were to try Xerces to parse these
> > > |file you would receive a parse error telling you that this encoding is
> > > |not supported. This is because Cp1252 is a java encoding and not an XML
> > > |supported one. Xerces will parse these files with this encoding but you
> > > |have to turn on one of its features. It will not work with jaxp using
> > > |xerces as you can't turn on features via jaxp.
> > > |
> > > |It's interesting to note that Sun itself ships j2ee ri xml descriptors
> > > |with this encoding. I really don't think they should.
> > > |
> > > |Just in case you guys planned to change your xml parser.
> > > |
> > > |Richard Backhouse
> > > |Oak Grove Software
> > > |
> > > |
