Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: [xsl] character entities

From: "Edward Bryant" <bryant_edward@----------->
To:
Date: 5/2/2005 2:50:00 PM
> So what is the accepted way to add character references to

> the output? Would I have to run some kind of find-and-replace script > 
after the XSLT transformation? What do other people do?



You shouldn't care whether characters in the output are represented as
themselves or as character references. No process that consumes the output
XML or HTML is going to make a distinction, so it doesn't matter. Leave it
to the serializer to decide. If you want to look at the output in a text
editor, choose an encoding that your text editor can handle, and the
serializer will do the rest.

Michael Kay
http://www.saxonica.com/

If that were true, it would be fine with me. I am not trying to output 
character references just for the sake of doing it. I was under the 
impression that I should try to do it because some browsers would have a 
problem with UFT-8 encoded data. Specifically, articles such as this one at 
A List Apart:



http://www.alistapart.com/articles/emen/



claim that "many more browsers choke on UTF-8 characters than do on named 
entities." Yet you claim that there is no distinction?



Is this true or isn't it?


transparent
Print
Mail
Like It
Disclaimer
.

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 www.altova.com/list/index.html. 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.

.
.

transparent

transparent