That's so crazy it just might work.
Actually, I can't think of any obvious reason why it wouldn't work. Just
use tunnel parameters to pass in the current style context and hey presto.
I'll give it a try.
Cheers,
Eliot
G. Ken Holman wrote:
At 2008-04-10 09:42 -0500, Eliot Kimber wrote:
<p>Some text <i>italic text <b>now bold italic</b> back to italic</i>
more text</p>
In the INCX representation of this, each text string with distinct
formatting is separately wrapped as a "text run", making the above into:
<txsr><pcnt>Some text </pcnt></txsr>
<txsr><pcnt>italic text </pcnt></txsr>
<txsr><pcnt>now bold italic</pcnt></txsr>
<txsr><pcnt> back to italic</pcnt></txsr>
<txsr><pcnt> more text& #x0a;</pcnt></txsr>
(INCX details omitted for simplicity)
An INCX file is essentially just a long sequence of txsr elements.
Doesn't the following address this for you implicitly:
<xsl:template match="text()">
<txsr>
<!--check ancestry for attributes-->
<pcnt>
<!--check ancestry for attributes-->
<xsl:value-of select="."/>
</pcnt>
</txsr>
</xsl:template>
Granted looking up the ancestry is slow, but using XSLT 2 you could
stuff tunnel parameters with cues and then check tunnelled values to
know what ancestry has been encountered ... that speeds things up
tremendously.
I hope this helps, or at least gives a direction to look in.
--
Eliot Kimber
Senior Solutions Architect
"Bringing Strategy, Content, and Technology Together"
Main: 610.631.6770
www.reallysi.com
www.rsuitecms.com
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--