Jim,

But your requirements are pretty well within what XSLT 1.0 will do, allowing
for how ugly the string processing is likely to be - so you're not completely
stuck.

I would recommend playing around with the XSLT in an online test environment -
there are a bunch that will run in your browser safely, or safely enough. XSLT
Fiddle or the functional equivalent.

If you need to brush up on XSLT, this list still retains a depth of 1.0
expertise - although please make that clear so no one is tempted to offer an
up-to-date solution you can't use.

Cheers, Wendell



From: ohaya ohaya@xxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Monday, July 22, 2024 3:20 PM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Cc: ohaya@xxxxxxxxx
Subject: Re:  Running xsltproc does not produce any output

Hi Wendell,

as I mentioned, this is being done in the context of a COTs (commercial
product), so we don't have much flexility as far as the XSLT version (more
precisely, it would be a LOT of other things involved, like approvals, etc.),
so I think we are stuck with XSLT 1.0, unless it is not possible.


FYI, I was trying to setup a test using XSLT and Java, and during that
process, I just realized that the XALAN that they were listing in that 3rd
party notice PDF is XALAN-C, and not XALAN Java.

I was noticing that version listed in their doc was "1.12", whereas the maven
repo was showing 2.7.x and was puzzling over that, when I noticed that there
was a separate XALAN-C package that had V1.12 :( ....

In retrospect, that kind of makes sense I guess... as I mentioned the CyberArk
software is on Windows....

So I think if we were to try to do extensions, I'd need to be working with
VC/VC++ ... which I don't think we will do...

So, "back to the drawing board" and try to see if I can do this with pure XSLT
1.0.   Not sure where to start though :( ....

Sigh...

Jim