Cart
[Home] [By Thread] [By Date] [Recent Entries]
It appears to me that the OP has a problem that could be remedied
simply enough through better modeling in the XML-that-is-not-yet-XML:
<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"/> would work better as: <j_entry cmd="admin/user/mail" rel="Mail Server" t="integer" ver="4.0" val="30"> <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'/>).</dsc> </j_entry> Then a template matching the dsc element would see its element contents, and being an element not an attribute, those contents would actually be legal. Cheers, Wendell At 10:23 AM 10/23/2007, you 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? ====================================================================== 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 ======================================================================
|
