[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] AW: Closing and reopening hierarchically structured e
Hi Michael, I must consider that I have quite some trouble explaining my special use case, but I'll try to build up a solution on basis of your recommendation. Thank you very much! wbr, Roman > -----Urspr|ngliche Nachricht----- > Von: Michael Kay [mailto:mike@xxxxxxxxxxxx] > Gesendet: Montag, 14. Februar 2005 14:34 > An: xsl-list@xxxxxxxxxxxxxxxxxxxxxx > Betreff: RE: Closing and reopening hierarchically > structured elements > > I haven't tried to study your particular problem, I'm afraid. > > The general design approach to these problems is to > > * start by defining the result tree that you want to produce > > * for each element node in the result tree, write a template > rule that outputs that element > > * then think about the conditions under which you want that > template rule to be fired, and write appropriate match > patterns and/or apply-templates instructions > > Michael Kay > http://www.saxonica.com/ > > > -----Original Message----- > > From: Huditsch Roman [mailto:Roman.Huditsch@xxxxxxxxxxxxx] > > Sent: 14 February 2005 13:28 > > To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx > > Subject: AW: Closing and reopening hierarchically structured > > elements > > > > Hi Michael, > > > > Thanks very much for your reply. > > Actually, I though about that before, but since I could not imagine > > any other solution and being absolutly desperate, I though > this would > > be my last escape route... > > My problem is that the table must appear at the same > logical position > > as before... > > How can the grouping mechanism help me at this position? > > Is there a simpler way in XSLT 2.0? > > > > Thanks very much for your patience. > > > > wbr, > > Roman > > > > > > > -----Urspr|ngliche Nachricht----- > > > Von: Michael Kay [mailto:mike@xxxxxxxxxxxx] > > > Gesendet: Montag, 14. Februar 2005 13:42 > > > An: xsl-list@xxxxxxxxxxxxxxxxxxxxxx > > > Betreff: RE: Closing and reopening hierarchically > structured > > > elements > > > > > > > The second step involves closing all ancestor elements > before my > > > > table. > > > > Generating an <fo:block span="all">, including my table > > > markup within > > > > and re-opening my closed ancestor elements (including all > > > attributes > > > > defined before). > > > > > > no, no! XSLT instructions write nodes to a tree, they > don't "open" > > > and "close" elements. Writing a node is an indivisible operation. > > > > > > Read http://www.jenitennison.com/xslt/grouping, and > > inwardly absorb... > > > > > > Michael Kay > > > http://www.saxonica.com/
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|