Re: Seeking a smarter tokenize for augmented text

Hi Trevor,

If the markup in the lines doesn't stretch across line breaks, you can 
insert empty elements for each line break using xsl:analyze-string in a 
first pass.

In the second pass, you then group the nodes below textlines, starting 
or ending with such an empty linebreak element that you introduced in 
the first pass.

Gerrit

On 06.05.2021 11:09, Trevor Nicholls [email protected] 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/3329386
or by email: [email protected]
--~--