Re: Fwd: How to stop XSLT from transforming &174; to s

Well, yes, when the parser works its magic on the source file, the character
references are converted to their proper characters for internal use of the
processor.  That's what is supposed to happen.

When the results are output, the processor is going to output the iso-8859-1
version of that character.  There are no means to inform it to turn the
character back into a character reference.  What character you will see when
you view the file depends on what display encoding is in use.

At least in the usual Windows encoding, #174 does give you the registered
sign, so it seems that the system is doing what it is supposed to.  This
means that you really do have a #174 character in the file.

Cheers,

Tom P

[B. Tommie Usdin]


> >To: XSL-List@xxxxxxxxxxxxxxxxxxxxxx
> >Subject: How to stop XSLT from transforming &174; to single character
> >From: carlson@xxxxxxxxxxxxxxxxx
> >
> >Hi,
> >I have looked at the FAQ and mailing list archives, but I still don't
> >get it.
> >
> >I have some xml source <name>joe user&174;</name>
> >I am trying to transform it to different formatted xml, but when I do,
> >the &174; entity gets converted to a single character, the registered
> >symbol.
> >I am using <xsl:value-of select="/name" disable-output-escaping="yes"/>
> >to get the value of the tag.
> >My out tag is <xsl:output method="xml" encoding="iso-8859-1/>.
> >
> >I am ultimately going to transform to HTML, so I want to keep the entity
> >in decimal form. Also, I get a problem when I get the xpath where the
> >parser throws an exception saying the <name> element  is missing an
> >end-tag for those <name> elements that have the single special character.
> >
> >
> >What I am trying to determine is, how can I leave the &174; as &174; in
> >the new xml.
> >
> >I am using xalan as my parser, but the same thing happens with msxml.
> >



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