- From: Piez, Wendell A. (Fed) <wendell.piez@nist.gov>
- Date: Fri, 10 Jan 2025 15:38:28 +0000
- To: XProc Dev <xproc-dev@w3.org>
Hello, Just restating the obvious here, but we can also make our own libraries for things we wish to handle 'declaratively' ... a grouping or wrapping operation, for example. If it is sufficiently generalized, your 'standard' is then already half baked (or at least proofing under a towel in a warm place). Cheers, Wendell -----Original Message----- From: Norm Tovey-Walsh <ndw@nwalsh.com> Sent: Thursday, January 9, 2025 10:19 AM To: denis.maier@unibe.ch Cc: gerrit.imsieke@le-tex.de; xproc-dev@w3.org Subject: Re: AW: p.wrap and attributes <denis.maier@unibe.ch> writes: > In a future xproc version, would it make sense to add something to cover the attributes here as well? Something like: Yes, perhaps. I tend (personally) to favor small, simple composable steps over large, complicated ones. After all, you've got access to XQuery or XSLT if you want to do something complicated. But in the steps that add elements, being able to specify attributes for those elements might make sense. Just in passing, I'll observe that the simpler-than-XSLT workaround is: <p:wrap match="xhtml:p[@class='reflist-item']" wrapper="ex:my-random-name" group-adjacent="@class"/> <p:set-attributes match="ex:may-random-name" .../> <p:rename match="ex:my-random-name" new-name="{{httpns}}div"/> Be seeing you, norm -- Norm Tovey-Walsh <ndw@nwalsh.com> https://norm.tovey-walsh.com/ > Life is pain...anyone who tells you differently is selling > something.--Wesley (The Princess Bride)
Received on Friday, 10 January 2025 15:38:36 UTC