On Tue, Nov 17, 2020 at 02:59:17PM -0000, Wendell Piez
wapiez(_at_)wendellpiez(_dot_)com scripsit:
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 ...
I like that!
Does it mean we'd need a generalized @select-string, @select-avt
distinction? Can't imagine anyone would go for breaking the
back-compatibility of @select, so @select would have to be a synonym of
@select-avt.
<xsl:map-entry key="'some-value'" select="'RELATED-VALUE'"/>
doesn't happen all that much but it sure feels like it when I have to
type it.
<xsl:map-entry key-string="some-value" select-string="RELATED-VALUE"/>
vs
<xsl:map-entry key-is-not-avt="true()" key="some-value"
select-is-not-avt="true()" select="RELATED-VALUE" />
seems like an obvious choice.
--
Graydon Saunders | graydonish(_at_)gmail(_dot_)com
Þæs oferéode, ðisses swá mæg.
-- Deor ("That passed, so may this.")
--~----------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
EasyUnsubscribe: http://lists.mulberrytech.com/unsub/xsl-list/1167547
or by email: xsl-list-unsub(_at_)lists(_dot_)mulberrytech(_dot_)com
--~--