Michael Kay wrote:
Hi
I think that (2) - a two-pass solution - is probably
the simplest to implement. Anything else would
involve changing the code you use to generate
the XSLT stylesheet, which you probably don't want
to make any more complex than it is already.
Actually, I'm writing the code that generate the XSLT scripts (XSLT
themself), so it's not a problem. And even in 2) I'll have to modify
it (but yes, more easily and localy). I'll give it a try and will make
some measurements.
For my culture, are you thinking about a specific technique for a
one-pass solution?
And for my culture again, is there no such counter functionality in
XSL-FO (that is, the "3)" in my previous email)?
Thanks for your help,
--drkm
___________________________________________________________________________
Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger
Téléchargez cette version sur http://fr.messenger.yahoo.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>
--~--