Closed RichardWallis closed 1 year ago
@RichardWallis I had the same issue, and was able to work around this in python by consulting this question: https://stackoverflow.com/questions/29443364/use-saxon-with-python ... the error has to do with saxon in python and one approach is to call saxon as a subprocess
import subprocess
subprocess.call(["saxon", "-o:output.xml", "-s:marc.xml", "./xsl/marc2bibframe2.xsl"])
Thanks to both; we accidentally put in a 2.0 function in our 1.0 stylesheet. We're converting it to exsl:node-set and it should be fixed soon.
Thanks for the headsup @ntra00.
Looking forward to the fix hoping it fits in with a looming deadline I have.
Can you grab a copy of the master branch and see if you can run 2.0 now, please? I've not tried it with xsltproc (and I'm out of time today), but I could replicate the issue with xalan and I have it running functioning with that processor.
If it looks good, we'll make a patch release.
@kefo Ran the master branch successfully locally both using xsltproc (on Mac) and with our Python based code using the lxml library.
Looks good!
Tried upgrading my current setup to the latest 2.0.0 release and got the following error in my Python environment:
Failed to evaluate the 'select' expression.
To see if the problem is in my code or in the released code I went back to basics:
... which seems to indicate the problem is in marc2bibframe2