Re: Analyze-string Regex to Match Content within Curly

Hi,

<xsl:analyze-string regex="\{.+?\}" interpret-attributes-as-avt="no"> ..

samish as?

<xsl:analyze-string regex-string="\{.+?\}"> ...

whereas the current @regex is a @regex-avt ...

Cheers, Wendell


On Tue, Nov 17, 2020 at 9:31 AM Graydon graydon@xxxxxxxxx <
xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:

> On Tue, Nov 17, 2020 at 01:57:30PM -0000, Michael Kay mike@xxxxxxxxxxxx
> scripsit:
> > A suggestion that I've thought about from time to time:
> >
> > If an attribute in XSLT expects an expression or an AVT, then a leading
> undoubled "}" in the attribute value indicates that is to be treated as a
> plain string.
> >
> > So for an expression
> >
> > <xsl:param name="x" select="}O'Reilly"/>
> >
> > indicates that the default value is the string "O'Reilly"
> >
> > and in an AVT
> >
> > regex="}[a-z]{4}"
> >
> > indicates that the regex is [a-z]{4}
> >
> > This relies on the fact that neither an AVT nor an expression can
> legally begin with an undoubled "}", nor is it ever likely to. And you can
> think of "}" as meaning "exit expression mode, here is plain text".
> >
> > Nice idea, or just too quirky?
>
> Perhaps more terse than quirky?
>
> Like David, I'd prefer to see switchable AVT interpretation via an
> attribute.  Single leading undoubled close brace is going to look like
> a mistake to my brain.
>
> What's the opposite of template?  "literal" is wrong,
> xsl:analyze-string/@regex still gets interpreted, just differently.
>
> @select-not-template or @regex-not-template as booleans?
>
> --
> Graydon Saunders  | graydonish@xxxxxxxxx
> CC&s oferC)ode, C0isses swC! mC&g.
> -- Deor  ("That passed, so may this.")
>
>


--
...Wendell Piez... ...wendell -at- nist -dot- gov...
...wendellpiez.com... ...pellucidliterature.org... ...pausepress.org...
...github.com/wendellpiez... ...gitlab.coko.foundation/wendell...