Subject: Re: [xsl] Value of variable not appearing in the <xsl:otherwise> of xml:choose From: "Graydon graydon@xxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> Date: Wed, 22 Sep 2021 17:16:37 -0000 |
On Wed, Sep 22, 2021 at 05:06:34PM -0000, Wendell Piez wapiez@xxxxxxxxxxxxxxx scripsit: > Another optimization to consider is to group using > group-adjacent="@class='analyze_visual'" returning a Boolean grouping key, > and groups that are nicely split. > > Then part/@num should collapse into '{position()}' and things get simpler. > Also gracefully handles the case of multiple splits. Especially if you find Wendell's observation above covers your use cases, it won't apply this time, but in general, I find that if I'm struggling with xsl:for-each-group, I should -- and sometimes I even do! -- remember that xsl:for-each-group is not fully general. There comes a time to write one's own recursive grouping function for this particular case. Which sounds awful, but is generally much simpler than it feels like it ought to be and is highly preferable to trying to make xsl:for-each-group cover a case it can't cover. -- Graydon Saunders | graydonish@xxxxxxxxx ^fs oferiode, pisses swa mfg. -- Deor ("That passed, so may this.")
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] Value of variable not app, Wendell Piez wapiez@ | Thread | Re: [xsl] Value of variable not app, Michael Kay mike@xxx |
Re: [xsl] Value of variable not app, Wendell Piez wapiez@ | Date | Re: [xsl] Value of variable not app, Michael Kay mike@xxx |
Month |