[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
Hi Matthew,
At 05:24 PM 6/3/2004, you wrote:
It's in the FAQ and the archives, but bears repeating. The 'disable-output-escaping' feature is optional: processors don't have to implement it. More to the point, what it really is is an instruction to the serializer that picks up the result tree and writes it out to a file (in XML syntax or whatever): there are architectures, such as Mozilla's client-side transformations or most XSL-FO pipelines, where no such file is written, but instead the result tree is just passed directly to some process to do something with it (such as format and display it). Naturally the "tag-writing" technique isn't going to work there, and disable-output-escaping won't have any effect.
That's too bad. In general, finding an output method (like "ascii" or "US-ASCII" or whatever your processor supports) that doesn't include upper-ASCII characters is a good way to compel the serializer to escape all non-ASCII characters as Unicode character references.
RE: [xsl] encoding shift_jis into an attribute
|
Subject: RE: [xsl] encoding shift_jis into an attribute From: Wendell Piez <wapiez@xxxxxxxxxxxxxxxx> Date: Thu, 03 Jun 2004 18:51:20 -0400 |
Hi Matthew,
At 05:24 PM 6/3/2004, you wrote:
I'm really only worried about one processing architecture, but I'm curious, what about the code I wrote isn't portable? I can see that building up tags as text is messy and error-prone, but I can't find any other way to achieve the same effect.
It's in the FAQ and the archives, but bears repeating. The 'disable-output-escaping' feature is optional: processors don't have to implement it. More to the point, what it really is is an instruction to the serializer that picks up the result tree and writes it out to a file (in XML syntax or whatever): there are architectures, such as Mozilla's client-side transformations or most XSL-FO pipelines, where no such file is written, but instead the result tree is just passed directly to some process to do something with it (such as format and display it). Naturally the "tag-writing" technique isn't going to work there, and disable-output-escaping won't have any effect.
You asked about setting the output encoding to "ascii". This doesn't seem to make any difference.
That's too bad. In general, finding an output method (like "ascii" or "US-ASCII" or whatever your processor supports) that doesn't include upper-ASCII characters is a good way to compel the serializer to escape all non-ASCII characters as Unicode character references.
Cheers, Wendell
====================================================================== Wendell Piez mailto:wapiez@xxxxxxxxxxxxxxxx Mulberry Technologies, Inc. http://www.mulberrytech.com 17 West Jefferson Street Direct Phone: 301/315-9635 Suite 207 Phone: 301/315-9631 Rockville, MD 20850 Fax: 301/315-8285 ---------------------------------------------------------------------- Mulberry Technologies: A Consultancy Specializing in SGML and XML ======================================================================
| Current Thread |
|---|
|
| <- Previous | Index | Next -> |
|---|---|---|
| RE: [xsl] encoding shift_jis into a, Matthew Simoneau | Thread | RE: [xsl] encoding shift_jis into a, Josh Canfield |
| XSLT help to generate FO-page-seque, Kenny Bogoe (BogoeMD | Date | RE: [xsl] encoding shift_jis into a, Josh Canfield |
| Month |