RE: Re: [xsl] About encoding - or something I relate to it ...

[cknell@xxxxxxxxxx]

It might help to diagnose the problem if your text editor had a HEX view so you could see the bytes that are being mapped to the ?. If yours doesn't have this feature, you could download a trial version of the editor I use (UltraEdit) to see this at http://www.idmcomp.com.
-- 
Charles Knell
cknell@xxxxxxxxxx - email



-----Original Message-----
From:     Karl Koch <TheRanger@xxxxxxx>
Sent:     Thu, 21 Jul 2005 16:04:14 +0200 (MEST)
To:       xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject:  Re: [xsl] About encoding - or something I relate to it ...

NO, the second effect does not mean that both # and $ have been mapped into
two questonmarks. It means basically that I don't know it. It could be both.
The data I have is the original one and there is no other. Also there is no
other person I could consult (e.g. the producer, somebody worked on it,
etc.). I am have what I have and that's it.

I am using Windows XP and IE to display it. I also have XMLSpy which also
dislays it like that. In the standard Windows text editor, I have also the
same display. Therefore I assume that this is not a result of the tool I am
using. However, I was "hoping" that somebody can tell me what when wrong
with the data in order to make me undo that in a organised way. However, now
I assume that the messing-up accident is not revertable since it is not a
one-to-one mapping (means many symbols have been mapped to ?? or ???).

Am I right in my assumption?

Karl



> --- Urspr|ngliche Nachricht ---
> Von: David Carlisle <davidc@xxxxxxxxx>
> An: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Betreff: Re: [xsl] About encoding - or something I relate to it ...
> Datum: Thu, 21 Jul 2005 14:42:36 +0100
> 
> 
> > Effect 2: I have questionmarks at places where I would expect to find a
> > special character
> 
> Are they really ? or are they just characters that your system does not
> understand and so renders as a ?.
> 
> > special character like ' or # or $. 
> 
> It's really odd that $ should get trashed as that is ascii.
> If both # and $ have really been transformed to two real ??
> and you need to convert them back then I'd say that your data is
> probably badly damaged and if at all possible I'd try to work backwards
> and re-obtain the original non-damaged data. If the characters are still
> distince but both showing as ?? then obviously you are in better shape
> to repare the damage. (same comments apply to your first point as well)
> 
> If you are using XSLT2 draft then you have regexp support , if you are
> using xslt1 then you need to fix your files (if they are fixable) with
> perl or sed (or xslt2) or some other program with regex support.
> (You could use xslt1 string handling but it is not really designed for
> that kind of general edit)
> 
> David
> 
> ________________________________________________________________________
> This e-mail has been scanned for all viruses by Star. The
> service is powered by MessageLabs. For more information on a proactive
> anti-virus service working around the clock, around the globe, visit:
> http://www.star.net.uk
> ________________________________________________________________________
> 

-- 
5 GB Mailbox, 50 FreeSMS http://www.gmx.net/de/go/promail
+++ GMX - die erste Adresse fo?=r Mail, Message, More +++