Altova Mailing List Archives

RE: [xsl] handling tags and PIs within a macro

From: "G. Ken Holman" <gkholman@-------------------->
Date: 10/23/2007 3:09:00 PM
At 2007-10-23 07:51 -0700, you wrote:
So how do you explain the fact that those macros are
parsed properly by the XSLTPROC

"properly"?  XSLTPROC is in error.

If what you quoted is precisely the text you have:

<j_entry cmd="admin/user/mail" dsc="Quota of a mailbox
in Megabytes. The default value is taken from the mail
server default quota (see entry <xref
linkend='mta_quota' xrefstyle='template:%t on page
%p'/>)." rel="Mail Server" t="integer" ver="4.0"

... then the naked "<" in the attribute is supposed to be rejected by 
a conforming processor.

What you have isn't XML: XML 1.0 production [10] "AttValue" 
specifically forbids a naked "<" character in an attribute.

Where is the confusion?

. . . . . . . . . . . . Ken

Comprehensive in-depth XSLT2/XSL-FO1.1 classes: Austin TX,Jan-2008
World-wide corporate, govt. & user group XML, XSL and UBL training
RSS feeds:     publicly-available developer resources and training
G. Ken Holman                 mailto:gkholman@xxxxxxxxxxxxxxxxxxxx
Crane Softwrights Ltd.
Box 266, Kars, Ontario CANADA K0A-2E0    +1(613)489-0999 (F:-0995)
Male Cancer Awareness Jul'07
Legal business disclaimers:


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.