Joe and Joris,

Again many thanks for the reply. What is confusing the crap out of me is 
that if I simply dump the xml to the client with the content type set to xml 
then the ie default style sheet "generally" parses the document fine. If 
however I parse the document with an xsl it craps out. I declare in the xml 
document and the xsl document the the encoding be utf-8 but this seems to 
have zero effect. 

I remember vaguely about some issue with the editor used but (somewhere in 
the dark recesses of my fried brain) I seem to recall that both homesite 
(editor in use by current employer) and note pad are both fine. (these are 
the text editors in use). Also the problem occurs both on server and client 
side execution. While not ruling anything out it seems odd to me but wouldn't 
be surprising that it would occur on two different machines (xp pro and win2k 
server) but that it doesn't happen using the default stylesheet built into 
ie. 

Am I missing something glaringly obvious here, being dense, or is there some 
workaround or way to determine the cause of the problem. I have looked around 
alot and found nothing (other than the aforementioned issue of editor and 
language pack problems (though not using anything other than utf-8 as 
declared)).

Any insight would be greatly appreciated. 

Thanks agian,

Jason

"Joris Gillis" wrote:

> Tempore 16:19:03, die Friday 07 January 2005 AD, hinc in foro {microsoft.public.xsl} scripsit Jason Burr <JasonBurr@d...>:
> 
> > Sorry about that I did have the xsl included in the code I tried (just a
> > typo when typing in here) sorry for the confusion. Anyway your right it works
> > with the snipped data that I posted. Turns out that the error was occuring
> > much later in the full xml document when encountering an é character and
> > thats the data I was testing with. I have had this issue alot and have no
> > idea why when encoding is set to utf-8 that this would cause a problem
> > usually I have control of the data source and replace any extended characters
> > like that but clearly thats not an option here any idea what to do to resolve
> > this?
> 
> You must make sure the encoding type of your editor and the encoding type you specify match.
> 
> During the process from fetching the RDF to storage on your hard drive (or in memory), some program (e.g. editor or browser) has probably altered the encoding type, thus resulting in an encoding type mismatch and accompanying errors.
> 
> -- 
> Joris Gillis (http://www.ticalc.org/cgi-bin/acct-view.cgi?userid=38041)
> "Quot capita, tot sententiae"  - Terentius , Phormio 454
>