Re: [xsl] Microsoft.XMLDOM UTF-8 Encoding!

["[Tech]" <tech@xxxxxxxxxxx>]

I work in a Latin environment since very a long time.
My user are any way latin iso-8859-1. So all works very well.

For better use I try to convert all my work to UTF-8 (for Flash purpose and
futur guest).

But, if I have to know the local encoding of my user, I'm not advanced with
this solution

I mist something or what?

----- Original Message ----- 
From: "Markus Abt" <abt@xxxxxxxx>
To: <xsl-list@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Saturday, July 12, 2003 12:26 PM
Subject: AW: [xsl] Microsoft.XMLDOM UTF-8 Encoding!


> Hello [Tech],
>
> I guess your problem is: the XML file you are generating is
> correct UTF-8, but it doesn't contain the right characters.
>
> I tried your web example. When I type in one non-ASCII character,
> then save the resulting XML source file, it contains 4 bytes for
> that character (which are displayed as 2 UTF-8 characters in the browser).
>
> Maybe the problem is this line of your code:
>   oEnreg.Text = request.form("texte")
>
> It looks like taking a UTF-8 text, misinterpreting it, and converting it
> later again to UTF-8 during the save.
>
> Your parsing and transforming in ASP seems to contain another bug
> (which Dimitre pointed out) which happens to eleminate the first one.
>
> Bye,
> Markus
> __________________________
> Markus Abt
> Comet Computer GmbH
> http://www.comet.de
>
>
> ----------
> Von: [Tech]
> Gesendet: Samstag, 12. Juli 2003 13:27
> An: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Betreff: Re: [xsl] Microsoft.XMLDOM UTF-8  Encoding!
>
> I repeat,
>
> I dont have problem to parse the XML. All caracters are UTF-8 encoding.
> So response.write(dom.transformNode(xsl)) show the writh thing!
>
> OK, let me show you!
>
> Go here : http://www.trucsweb.com/rss/sauve3.asp
> You can enter all non-us car and it will be UTF-8.
> You see it's work good.
>
> But try open the xml file directly in IE (or Mozilla the same)...
> tx
>
>
> ----- Original Message ----- 
> From: "Julian Reschke" <julian.reschke@xxxxxx>
> To: <xsl-list@xxxxxxxxxxxxxxxxxxxxxx>
> Sent: Saturday, July 12, 2003 2:57 AM
> Subject: RE: [xsl] Microsoft.XMLDOM UTF-8 Encoding!
>
>
> > > From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> > > [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of [Tech]
> > > Sent: Saturday, July 12, 2003 1:03 AM
> > > To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> > > Subject: Re: [xsl] Microsoft.XMLDOM UTF-8 Encoding!
> > >
> > >
> > > Exact,
> > >
> > > The first byte supose to tell the encoding.
> >
> > The first bytes *may* tell the encoding.
> >
> > > Like this UTF-16 => "Unicode byte-order mark [0xFF 0xFE] or [0xFE
0xFF]"
> > >
> > > But Microsoft (and lot more) say that XML file generate with ASP
> > > and XMLDOM
> > > are UTF-8 by default. (no byte was added to the file...)
> >
> > It doesn't need to.
> >
> > > So, How tell "Microsoft.XMLDOM" to save my XML file with a true UTF-8
> > > encoding?
> >
> > To *save* a DOM in UTF-8, do what you're already doing (create the XML
> > declaration using MSXML's createProcessingInstruction() and save the
> file).
> >
> > However the issue seems to be *serving* XML to a client. You'll need to
> show
> > us *that* ASP code to find the problem. It's almost certainly an
> unnecessary
> > round-trip of the XML serialization trough a string, such as
> >
> > response.write(dom.xml)
> >
> > or
> >
> > response.write(dom1.transformNode(dom2))
> >
> > which *will* break encoding information.
> >
> > Julian
> >
> > --
> > <green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
> >
> >
> >  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> >
> >
>
>
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
>
>
>
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
>
>


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list