Re: [xsl] How to tokenize a comma-separated CSV record which has a field containing a string that has commas?

Subject: Re: [xsl] How to tokenize a comma-separated CSV record which has a field containing a string that has commas?
From: "Martin Honnen martin.honnen@xxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Date: Thu, 4 Aug 2022 20:17:16 -0000
On 04.08.2022 21:59, Michael Kay mike@xxxxxxxxxxxx wrote:
A good case for Invisible XML (topic of the week at Balisage), but
I'll leave someone else to flesh it out.

Yes, need you to flesh out

B on-no-match="shallow-copy-all"

of
https://balisage.net/Proceedings/vol27/html/Kay01/BalisageVol27-Kay01.html#d1
0153e637
instead, the paper says

For arrays, it does

<xsl:apply-templates select="array:parcels(.)" mode="#current"/>

that is, it wraps each of the array members into a parcel and processes
each one separately.

For maps, it does:

<xsl:apply-templates select="map:entries()" mode="#current"/>


But I don't grasp how that initiates "the action of the default template rule here is to construct a new array or map from the values returned by the selected template rules"?


How are the arrays or maps created, doesn't that require use of xsl:map and xsl:array?

Is <xsl:mode on-no-match="shallow-copy-all"/> behaviour definable with
current or future XSLT elements?

Current Thread