 |
|
|
The vendor recommends a UTF-8 encoded file. So when I create an XML
file (before any XSLT is applied) I get just square boxes where those
math symbols and other items usually appear. I think this is why they
require the use of an entity. Does that make more sense or am I still
missing the point?
<chad/>
Chad Chelius
AGI Training
cchelius@xxxxxxxxxxxxxxx
On Jul 3, 2006, at 10:39 AM, David Carlisle wrote:
Nothing there suggests the need for entities in the XSLT output.
If you have an entity reference & f o o b a r ; in the file and that
entity is defined by a DTD to be __something__ then when your vendor
processes the XMl file, the XML parser will (or should) report the
same
thing whether the file has & f o o b a r ; or __something__ in it.
An entity reference is indistinguishable from the direct use of the
entity which it references.
If the vendor tools require an ASCII encoded file taht's a different
matter and can be addressed by
<xsl:output encoding="US-ASCII"/>
David
|
|
| |
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.
| |
| |
|
|
|
