[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
Jelmer,
This is a tough problem.
Take a look at the thread in the archive "Extracting a verse" from last December, starting at http://www.biglist.com/lists/xsl-list/archives/200212/msg00814.html.
Personally, *if* you are always serializing your output (e.g. never running a transform in a display engine but always writing a file), I find David Carlisle's solution there to be nice and elegant. Use at your own risk, of course.
A true XSLT-based solution, which does not rely on writing tags to output (an option that should hardly be mentioned, and never condoned, though David and now I have suggested it), is *hard* -- a couple of people in that thread took a stab at it, but I haven't been able to take the time to satisfy myself that it's actually been solved.
You may also want to think of non-XSLT solutions. Your processing requirement runs right up against XML's representing a single tree -- in your case, the wrong one. The reason this problem is not more common than it is is that most XML projects do not try to represent multiple hierarchies in their markup. TEI projects being the notable exception.
If you are a member of the TEI, you might take this question to TEI-L (http://listserv.brown.edu/archives/tei-l.html), where a number of experienced practitioners may be able to help. If you're not a member -- join!
"At 07:50 PM 8/20/2003, you wrote:
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Re: [xsl] pagebreak between elements
Subject: Re: [xsl] pagebreak between elements From: Wendell Piez <wapiez@xxxxxxxxxxxxxxxx> Date: Thu, 21 Aug 2003 12:21:41 -0400 |
Jelmer,
This is a tough problem.
Take a look at the thread in the archive "Extracting a verse" from last December, starting at http://www.biglist.com/lists/xsl-list/archives/200212/msg00814.html.
Personally, *if* you are always serializing your output (e.g. never running a transform in a display engine but always writing a file), I find David Carlisle's solution there to be nice and elegant. Use at your own risk, of course.
A true XSLT-based solution, which does not rely on writing tags to output (an option that should hardly be mentioned, and never condoned, though David and now I have suggested it), is *hard* -- a couple of people in that thread took a stab at it, but I haven't been able to take the time to satisfy myself that it's actually been solved.
You may also want to think of non-XSLT solutions. Your processing requirement runs right up against XML's representing a single tree -- in your case, the wrong one. The reason this problem is not more common than it is is that most XML projects do not try to represent multiple hierarchies in their markup. TEI projects being the notable exception.
If you are a member of the TEI, you might take this question to TEI-L (http://listserv.brown.edu/archives/tei-l.html), where a number of experienced practitioners may be able to help. If you're not a member -- join!
Good luck, Wendell
"At 07:50 PM 8/20/2003, you wrote:
the problem is that TEI uses <pb /> (pagebreak) elements to seperate pages
====================================================================== 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 ======================================================================
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
[xsl] pagebreak between elements, jelmer | Thread | [xsl] cannot include global level v, Chang, Shining |
Re: [xsl] Column Heads and Column D, Wendell Piez | Date | RE: [xsl] text output encoding UTF-, Michael Kay |
Month |