Re: [xsl] Running xsltproc does not produce any output

["Piez, Wendell A. (Fed) wendell.piez@xxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>]

Jim,

I proposed looking at a "Fiddle" only as a way of assessing capabilities of
versions (note plural) of XSLT with respect to your issue.

If you know that your solution must run in a given processor supporting XSLT
1.0, then you are (a) stuck without regular expressions, while not stuck
altogether, as Liam demonstrates, while (b) an XSLT 1.0 Fiddle could be a way
to try and test your XSLT that *might* be easier than alternative workflows
(at least for assessment if not development).

XSLT 1.0 does not support regular expressions, but it is available in your
browser - see a project I set up here: https://pages.nist.gov/xslt-blender/
(most of the projects either target verticals, or remain quite crude - ymmv) -
all the code is open.

It doesn't offer a Fiddle - I'd recommend a link but I can hardly keep up with
Martin H -- although it could provide a back end for one. (An XSLT 1.0 Fiddle
not a more recent XSLT - the engine being in the browser.) But it was made in
the spirit of "XSLT 1.0 still has its uses for certain niches", and yours
might be one of those.

Enjoy, Wendell


From: ohaya ohaya@xxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Tuesday, July 23, 2024 8:33 AM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: [xsl] Running xsltproc does not produce any output

Hi,

If xsltproc won't work (because no regex extension), then I think that maybe
that XSLT Fiddle website that Wendell suggested in his message might work?

Jim




On Tuesday, July 23, 2024 at 07:31:45 AM EDT, ohaya
<ohaya@xxxxxxxxx<mailto:ohaya@xxxxxxxxx>> wrote:


Hi,

This is what I get when I run xsltproc --dumpextensions:

[root@nodejs ~]# xsltproc --dumpextensions
Registered XSLT Extensions
--------------------------
Registered Extension Functions:
{http://exslt.org/common}object-type
{http://exslt.org/math}max
{http://exslt.org/math}power
{http://exslt.org/math}cos
{http://exslt.org/sets}has-same-node
{http://exslt.org/sets}leading
{http://exslt.org/strings}decode-uri
{http://exslt.org/strings}replace
{http://exslt.org/dates-and-times}add-duration
{http://exslt.org/dates-and-times}date-time
{http://exslt.org/dates-and-times}day-abbreviation
{http://exslt.org/dates-and-times}year
{http://exslt.org/crypto}md5
{http://exslt.org/math}lowest
{http://exslt.org/math}atan
{http://exslt.org/strings}tokenize
{http://exslt.org/dates-and-times}date
{http://exslt.org/dates-and-times}difference
{http://exslt.org/dates-and-times}week-in-month
{http://exslt.org/crypto}rc4_decrypt
{http://exslt.org/sets}difference
{http://exslt.org/dates-and-times}day-in-month
{http://icl.com/saxon}line-number
{http://exslt.org/math}random
{http://exslt.org/sets}distinct
{http://exslt.org/sets}trailing
{http://exslt.org/dates-and-times}day-in-year
{http://exslt.org/dates-and-times}month-name
{http://exslt.org/dates-and-times}second-in-minute
{http://exslt.org/dates-and-times}seconds
{http://icl.com/saxon}evaluate
{http://exslt.org/common}node-set
{http://exslt.org/math}highest
{http://exslt.org/math}tan
{http://exslt.org/strings}split
{http://exslt.org/strings}encode-uri
{http://exslt.org/strings}padding
{http://exslt.org/dates-and-times}day-name
{http://exslt.org/dates-and-times}leap-year
{http://exslt.org/math}abs
{http://exslt.org/math}sin
{http://exslt.org/math}exp
{http://exslt.org/dates-and-times}month-abbreviation
{http://exslt.org/dates-and-times}week-in-year
{http://icl.com/saxon}expression
{http://exslt.org/crypto}rc4_encrypt
{http://exslt.org/dates-and-times}day-in-week
{http://exslt.org/dates-and-times}duration
{http://exslt.org/dates-and-times}minute-in-hour
{http://exslt.org/dates-and-times}month-in-year
{http://exslt.org/dynamic}evaluate
{http://exslt.org/math}atan2
{http://exslt.org/dates-and-times}add
{http://exslt.org/dates-and-times}day-of-week-in-month
{http://exslt.org/dates-and-times}time
{http://exslt.org/crypto}sha1
{http://exslt.org/math}min
{http://exslt.org/math}constant
{http://exslt.org/math}log
{http://exslt.org/math}asin
{http://exslt.org/math}acos
{http://exslt.org/sets}intersection
{http://exslt.org/strings}align
{http://exslt.org/strings}concat
{http://exslt.org/dates-and-times}hour-in-day
{http://exslt.org/dates-and-times}sum
{http://icl.com/saxon}eval
{http://exslt.org/dynamic}map
{http://xmlsoft.org/XSLT/}test
{http://exslt.org/crypto}md4
{http://exslt.org/math}sqrt

Registered Extension Elements:
{http://xmlsoft.org/XSLT/}test
{http://exslt.org/common}document
{http://exslt.org/functions}result

Registered Extension Modules:
http://icl.com/saxon
http://exslt.org/functions
http://xmlsoft.org/XSLT/




On Tuesday, July 23, 2024 at 12:00:42 AM EDT, Liam R. E. Quin
<liam@xxxxxxxxxxxxxxxx<mailto:liam@xxxxxxxxxxxxxxxx>> wrote:


On Tue, 2024-07-23 at 03:01 +0000, ohaya
ohaya@xxxxxxxxx<mailto:ohaya@xxxxxxxxx> wrote:

>
> So I was looking at a regex that would check for that (2 strings same
> length) and found this:

>

I forgot to add, i don't think xsltproc supports regular expressions.
They are not in XSLT 1 (or XPath 1), although xsltproc does have some
extensions;
xsltproc --dumpextensions
will list them.

liam

--
Liam Quin, https://www.delightfulcomputing.com/
Available for XML/Document/Information Architecture/XSLT/
XSL/XQuery/Web/Text Processing/A11Y training, work & consulting.
Barefoot Web-slave, antique illustrations:
http://www.fromoldbooks.org<http://www.fromoldbooks.org/>

XSL-List info and archive<http://www.mulberrytech.com/xsl/xsl-list>
EasyUnsubscribe<http://lists.mulberrytech.com/unsub/xsl-list/3302254> (by
email<>)