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

[Nancy Brandt <nancy_brndt@xxxxxxxxx>]

Hi dear Charles,

Macros in our documentation are similar to entities.
You define the entity's pattern (contents) somewhere
and place the name of the entity within an XML-wrapped
text and then the compiler parses the entity according
to its defined contents. The error is triggered by
such common Docbook XML's tags as <sbr/>, <command> --
they are pure Docbook XML formatting items...

Regards,
Nancy 
--- cknell@xxxxxxxxxx wrote:

> I'm not familiar with the concept of a "macro" in
> the context of XSLT. Is this an extension function
> of a particular XSLT processor?
> 
> Your processor is simply reporting that what you've
> written is not XML ("Unescaped '<' not allowed in
> attributes values.").
> 
> If this macro is a feature of a particular processor
> (XML, XSLT?), then you may have better luck in
> getting an answer on how to break the rules on the
> support list for that processor. 
> 
> So far you don't seem to have got very far on this
> list, probably because the readers don't understand
> the background of your situation (e.g., what
> programs are you using to process the data documents
> and stylesheets, how are you calling them, what is
> the purpose of the macro, how the macro is supposed
> to function, etc.).
> 
> 
> -- 
> Charles Knell
> cknell@xxxxxxxxxx - email
> 
> 
> 
> -----Original Message-----
> From:     Nancy Brandt <nancy_brndt@xxxxxxxxx>
> Sent:     Tue, 23 Oct 2007 07:09:51 -0700 (PDT)
> To:       xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject:  [xsl] handling tags and PIs within a macro
> 
> Hi guys,
> 
> I have created templates by the help of which, the
> compiler will parse my macros for graphics, chunks
> of
> table entries, etc. The problem is that when a macro
> is parsed by its template defined in .xsl file, the
> compiler cannot handle such processing instructions
> as
> <sbr\>, <xref.../>  <command>, etc that are within
> the
> macro's text. The compiler says:
> parser error :  How do I create a template within
> each macro
> template, so that those processing instructions in
> the
> <> format will be handled regularly, without
> changing
> their format to <...>?
> 
> Please, advise!
> 
> P.S. here is an example of a table row macro (and
> within this row there could be all these problematic
> PIs.
> 
> <xsl:template match="j_entry">
> <row>
>   <entry>
>   <xsl:element name="formalpara">
>     <xsl:attribute name="id">
>       <xsl:value-of select="@fid"/>
>      </xsl:attribute>
>      <title>
>        <xsl:value-of select="@cmd"/>
>      </title>
>   </xsl:element>
> 
>   <formalpara>
>     <title>Description</title>
>     <xsl:value-of select="@dsc"/>
>   </formalpara>
> 
>   <formalpara>
>     <title>Relevant to</title>
>     <xsl:value-of select="@rel"/>
>   </formalpara>
> 
>   <formalpara>
>     <title>Type</title>
>     <xsl:value-of select="@t"/>
>   </formalpara>
>   
>   <formalpara>
>     <title>Default Value</title>
>     <xsl:value-of select="@val"/>
>   </formalpara>
>   </entry>
> </row>
> </xsl:template>
> 
> The macro in the XML source file looks like this:
> 
> <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"
> val="30"/>
> 
> Thanks in advance!
> Kind regard,
> Nancy
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam
> protection around 
> http://mail.yahoo.com 
> 
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com