Re: [xsl] Seeking a smarter tokenize for augmented text

["Michael Kay mike@xxxxxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>]

There seem to be two broad strategies for this kind of problem:

(a) process the text nodes to insert "markup" structure, e.g. replace newlines
by <nl/>, and then process as nodes, e.g. using for-each group-starting="nl".

(b) process the embedded elements converting them to text, e.g. convert
<var>line</var> to %line%, then process as text, then reconstitute the
markup.

For this example, (a) seems easier.

Michael Kay
Saxonica

> On 6 May 2021, at 10:09, Trevor Nicholls trevor@xxxxxxxxxxxxxxxxxx
<xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:
>
> Hi
>
> Turning xml like this:
>
> <textlines>this is line 1
> this is line 2
> this is line 3</textlines>
>
> into something like this:
>
> <textlines>
> <line>this is line 1</line>
> <line>this is line 2</line>
> <line>this is line 3</line>
> </textlines>
>
> is simple and I have functions that do it. But they rely on <textlines>
being an xs:string, which is processed by a trivial function I wrote:
>
> <xsl:function name="my:intoLines" as="xs:string*">
>   <xsl:param name="arg" as="xs:string?" />
>   <xsl:sequence select="tokenize( $arg, '(\r\n?|\n\r?)' )" />
> </xsl:function>
>
> I would like to extend this so that it can handle an element consisting of
text lines with some embedded markup (there won't be much, but there will be
some). For example, taking:
>
> <textlines>this is line <seq>1</seq>
> this is <var>line</var> 2
> this <emph>is</emph> line 3</textlines>
>
> and producing
>
> <textlines>
> <line>this is line <seq>1</seq></line>
> <line>this is <var>line</var> 2</line>
> <line>this <emph>is</emph> line 3</line>
> </textlines>
>
> Sequence and tokenize isn't adequate but is there a way to do this that
won't overtax my brain too much?
>
> cheers
> T
> XSL-List info and archive <http://www.mulberrytech.com/xsl/xsl-list>
> EasyUnsubscribe <http://lists.mulberrytech.com/unsub/xsl-list/293509> (by
email <>)