RE: [xsl] string replace with ­

Subject: RE: [xsl] string replace with ­
From: ronald heller <ronald@xxxxxxxxxxx>
Date: Mon, 05 Nov 2001 14:37:13 +0100
IMHO I don't think mutliple xsl would be a strange thing to do here.

Sometimes I make use of the mode attribute on templates to ensure different output files.
The problem when setting the output top be html is that when also generating xml, the result is "html optimized"
That would mean that any "html" element in the xml also is html optimized.

That's sounds to me as dangerous, and most likely not what you want.
Just thought I'd mention it.

At 08:17 AM 11/5/01 -0500, you wrote:
Thanks. This was an encoding problem.

This problem arose here because I have a single XSLT file outputting multiple HTML and XML files. It
looks like I can only set the xsl:output parameters once, as opposed to setting them for each
specific output file. So a bad guess initially, caused the problem mentioned before.

Perhaps this is just a design problem on my part but how do people handle outputting multiple files
that are different types (XML, HTML) from a single XSL file?

I am processing a single XML file into several HTML renditions and into one XML file that summarizes
the first XML file. Should I be using multiple XSL files so that I can properly manage the output
file types? I have been avoiding that since it would require reading the input XML file multiple

-----Original Message----- From: David Carlisle [mailto:davidc@xxxxxxxxx] Sent: Friday, November 02, 2001 7:19 PM To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx Subject: Re: [xsl] string replace with &shy;

should have been translated to


but becomes


did you really mean an A or was it an accented A? In the latter case
you are presumably writing out the file in utf-8 encoding in which case
most characters in that range are encoded as multiple bytes the first of
which looks like an accented A if you mis-read the file in a latin-1

As I mentioned this is discussed often at length on any thread about
nbsp. But basically either correct the configuration of your browser so
it recognises utf-8, or write out the file in latin-1 by adding
<xsl:output encoding="iso-8859-1"/> to your stylesheet.


_____________________________________________________________________ This message has been checked for all known viruses by Star Internet delivered through the MessageLabs Virus Scanning Service. For further information visit or alternatively call Star Internet for details on the Virus Scanning Service.

XSL-List info and archive:

XSL-List info and archive:

XSL-List info and archive:

Current Thread