Am 10.02.2022 um 09:40 schrieb Imsieke, Gerrit, le-tex
gerrit(_dot_)imsieke(_at_)le-tex(_dot_)de:
Hi Matthieu,
At XML Prague 2019, I presented what I call the "upward projection
method" [1, 2]. It turned out that Wendell Piez had independently
developed his own upward projection approach [3, 4]. Both methods
group the leaf nodes, starting at the splitting points.
Gerrit
[1]
https://archive.xmlprague.cz/2019/files/xmlprague-2019-proceedings.pdf#page=347
[2]
https://subversion.le-tex.de/common/presentations/2019-02-09_xmlprague_xslt-upward-projection/slides/index.html
I think Gerrit's approach will help you although I think your set of
restricted-to nodes will be adapted slightly, instead of
current-group()/ancestor-or-self::node()
it seems you want to carry over the section/title from each section.
[3]
https://github.com/wendellpiez/MITH_XSLT/blob/master/xslt/p-promote.xsl
[4]
https://www.biglist.com/lists/lists.mulberrytech.com/xsl-list/archives/202008/msg00076.html
On 10.02.2022 09:20, Matthieu Ricaud-Dussarget ricaudm(_at_)gmail(_dot_)com
wrote:
Dear XSL List,
It's not the first time I'm facing a splitting problem working with
publishing documents.
I used to find kind of tricky/verbose solutions but I'm wondering if
I'm missing something obvious, especially with XSLT 3.0 new features ?
My XML looks like this :
<root>
<section>
<title>Title</title>
<content>
<p>paragraph #1</p>
<p>paragraph #2 to split <split id="split-1"/> here</p>
<p>paragraph #3</p>
<p>paragraph #4 <strong> to split <split id="split-2"/>
here</strong> if possible</p>
<p>paragraph #5</p>
<ul>
<li>Item #1</li>
<li>Item #2 to split <split id="split-3"/> here</li>
<li>Item #3</li>
<li>
<ul>
<li>Item #4</li>
<li>Item #5 to <em>split <split id="split-4"/></em> here
if possible</li>
<li>Item #6</li>
</ul>
</li>
</ul>
<p>paragraph #6</p>
</content>
</section>
</root>
The goal is to split the section on every <split> element (just like
a page would break the flowing text anywhere in the structure).
Expected result :
<root>
<section>
<title>Title</title>
<content>
<p>paragraph #1</p>
<p>paragraph #2 to split</p>
</content>
</section>
<split id="split-1"/>
<section>
<title>Title</title>
<content>
<p>paragraph #3</p>
<p>paragraph #4 <strong> to split</strong></p>
</content>
</section>
<split id="split-2"/>
<section>
<title>Title</title>
<content>
<p><strong> here</strong> if possible</p>
<p>paragraph #5</p>
<ul>
<li>Item #1</li>
<li>Item #2 to split </li>
</ul>
</content>
</section>
<split id="split-3"/>
<section>
<title>Title</title>
<content>
<ul>
<li> here</li>
<li>Item #3</li>
<li>
<ul>
<li>Item #4</li>
<li>Item #5 to <em>split</em></li>
</ul>
</li>
</ul>
</content>
</section>
<split id="split-4"/>
<section>
<title>Title</title>
<content>
<ul>
<ul>
<li> here if possible</li>
</ul>
<li>Item #6</li>
</ul>
<p>paragraph #6</p>
</content>
</section>
</root>
My idea was to iterate from 1 to the number of split elements + 1 and
working on the section with tunnel params so I can test for each node
if it's before / after / in between (current) splits elements, and
then decide to keep the node or not according to this position.
I already used this kind of solution on a similar problem, long time
ago. So I'll give it a try though I'm not not totally confident with
it (because split elements can appear as inline content here).
Please let me know if you have ideas, if my solution is the right or
wrong way to go?
Are there special design patterns for this kind of problem ?
And last, have you ever faced this kind of splitting issue, any
feedback welcome :)
Cheers,
Matthieu Ricaud-Dussarget
--~----------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
EasyUnsubscribe: http://lists.mulberrytech.com/unsub/xsl-list/1167547
or by email: xsl-list-unsub(_at_)lists(_dot_)mulberrytech(_dot_)com
--~--