Altova Mailing List Archives

[xsl] =?iso-8859-1?Q?Re=3A_ =3B_is_being_displayed_as_=C1?=

From: "Swen Thuemmler" <Swen.Thuemmler@------------>
Date: 12/12/2001 12:09:00 AM
On Tue, 11 Dec 2001, Brinkman, Theodore wrote:

> And, how would you suggest someone actually get '&nbsp;' into the output in
> order to avoid  the issue which started this thread in the first place?
> (browsers assuming a different encoding type than is sent, and therefore
> mistranslating character 160 as '&Aacute;' instead of ' '?  I have yet to see a
> browser which misunderstands '&nbsp;'.

You could use <xsl:output method="html" encoding="us-ascii"/>

This should solve most output encoding problems (assuming your XSL
processor supports US-ASCII, but most do). This way, &#160; will be output
as either &nbsp; or &#160; which all browsers recognize (I've not seen any
browser which does not recognize it). The drawback is, that all characters
which are not in US-ASCII are encoded as either HTML-Entities or numeric


 XSL-List info and archive:


These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.