RE: [xsl] url encoding gets wrong with åöä?

["XSLList" <XSLList@xxxxxxxxxx>]

Niklas,

I have been watching this thread with interest.

Perhaps you could try a dedicated XML editor like XMLSpy, we have a continuing
battle with encoding due to the way MSXML handles bit streams and XMLSpy has
proved to be invaluable, that and a good hexeditor so that you can track where
the "corruption" occurs.


William Charlton
The yMonda team
yMonda Limited
w: www.ymonda.net

-----Original Message-----
From: Niklas Holmberg [mailto:Niklas.Holmberg@xxxxxxxxx]
Sent: 2006 June 09 09:03
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: RE: [xsl] url encoding gets wrong with C%C6C$?


Hmm, there is no BOM in my output...
Don't know what to do about this anymore. Never thought it would be this much
trouble =)

/Niklas

-----Original Message-----
From: bryan rasmussen [mailto:rasmussen.bryan@xxxxxxxxx]
Sent: den 9 juni 2006 09:54
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: [xsl] url encoding gets wrong with C%C6C$?

Well, as long as you're checking in the hex editor you should be able to see
the byte order mark, if there is one, compare this with your declared encoding
etc. However I suppose that this won't be a problem since, IIRC, 3F  == ?.

At this point I would assume that the problem was not at the xslt level but
higher up; protocol level,  server side programming, something that is
handling your xml before it gets sent to the xslt.



Cheers,
Bryan

On 6/9/06, Niklas Holmberg <Niklas.Holmberg@xxxxxxxxx> wrote:
>
> Checked in a hex editor and each CCCC%C$C6 is shown as "??" (3F 3F).
> Any suggestions from there?
>
> /Niklas
>
> -----Original Message-----
> From: andrew welch [mailto:andrew.j.welch@xxxxxxxxx]
> Sent: den 8 juni 2006 14:22
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: Re: [xsl] url encoding gets wrong with C%C6C$?
>
> On 6/8/06, Niklas Holmberg <Niklas.Holmberg@xxxxxxxxx> wrote:
> >
> > It's not the browser that is the problem. It's the xslt output that
doesn't get right. I get the characters ?? instead of WWW&. "AffWrsluncher"
commes out as "Aff??rsluncher".
>
> How can you be sure?  When the application you are viewing the result in
doesn't having a mapping in the specified encoding for the byte sequence, it
may use a ? equally if it does have a mapping but the font you are using
doesn't have a glyph for the character then it may use a ?
>
> The only to way know for certain is to check the bytes using a hex editor -
if the byte is 0x3F then it really is a question mark, otherwise it's just one
of the above reasons.
>
> cheers
> andrew
>
>
>
>
> Confidentiality Notice: This e-mail transmission may contain confidential or
legally privileged information that is intended only for the individual or
entity named in the e-mail address. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or reliance
upon the contents of this e-mail is strictly prohibited and may be unlawful.
If you have received this e-mail in error, please notify the sender
immediately by return e-mail and delete all copies of this message.
>




Confidentiality Notice: This e-mail transmission may contain confidential or
legally privileged information that is intended only for the individual or
entity named in the e-mail address. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or reliance
upon the contents of this e-mail is strictly prohibited and may be unlawful.
If you have received this e-mail in error, please notify the sender
immediately by return e-mail and delete all copies of this message.