[
Lists Home |
Date Index |
Thread Index
]
Probably you are specifying the output to be encoded in UTF-8 or
something like that where the character is supported in the encoding.
In that case the output should also contain the encoding indicated in
the xml header (e.g. <? xml ... encoding="UTF-8"?>) There's nothing
wrong with that, further XSLT processing should be able to handle it
just fine. Some editors or viewers might not be reading the xml header,
though, in which case they wouldn't necessarily realize the file is in
UTF-8 and might display garbage. In that case, use a setting in the
editor to reinterpret the file as UTF-8 and all should be well.
If you set output="html" in XSLT you should get the character entities
though BTW.
Simon
On Thursday, May 22, 2003, at 11:04 AM, Sascha Pogacar (XPECT MEDIA)
wrote:
> Hello, I encounter a xslt-problem, which should be easy, but I dont
> find an solution.
>
> I have some XML-Files which I am processing through an XSLT (on an
> IIS5 with MSXML 4.0) to split the files into various different other
> XML-Files.
>
> My problem is the automatic transformation of the charachter entities
> like &#nnnn; into whatever character they represent, with the result
> of skrewed up content in the end.
>
> Is there someone out there who knows a solution for this, without
> using CDATA.
>
> thanks
> Sascha Pogacar
>
>
>
--
anti-spam: do not post this address publicly
www.simonwoodside.com -- 99% Devil, 1% Angel
|
