Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mei2musicxml and saxon-specific functions #25

Open
mfeustle opened this issue Jul 25, 2021 · 3 comments
Open

mei2musicxml and saxon-specific functions #25

mfeustle opened this issue Jul 25, 2021 · 3 comments
Assignees

Comments

@mfeustle
Copy link

Trying to run the mei2musicxml XSL in Meico generates an error referring to saxon functions. In another XML tool, it simply returns no response. I see where the tool for the reverse process, musicxml2mei, recently had a new version added that removed saxon-specific functions. There is definitely a need for the same on mei2musicxml.

@musicEnfanthen
Copy link
Member

@mfeustle Thanks for bringing this up, and apologies for the long delay.

@kepper Could you have a look please?

@kepper
Copy link
Member

kepper commented Apr 8, 2022

I had a brief first look, but that look indicates that the problems solved in #23 do not apply to mei2musicxml – the same saxon-specific function isn't used here. It would therefore be helpful to see the error messages. In general, I'm not sure about the state of mei2musicxml at all – it clearly predates MEI Basic, and thus has the problem of having to unify MEI before it gets converted. Some things in MEI just cannot be unified like this (choices, readings, …), so there's a quite significant conceptual challenge involved, that always slowed down development of this XSLT. I'm willing to pick it up again, but only when starting from MEI Basic. But that's a mid-term thing – for now, I'm happy to see if there's a way to fix problems short-term. This requires error messages and ideally the MEI files used. Happy to receive those as private messages on Slack or by mail…

@musicEnfanthen
Copy link
Member

@mfeustle Any chance that you are still able to reproduce the error messages from last summer?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants