8000 Changes to work with Saxon 9.9 (but not Saxon 10). by tgraham-antenna · Pull Request #5 · xmlark/xslthl · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Changes to work with Saxon 9.9 (but not Saxon 10). #5

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Changes to work with Saxon 9.9 (but not Saxon 10). #5

wants to merge 1 commit into from

Conversation

tgraham-antenna
Copy link
Contributor

If not using a Saxon config file, the initializer needs to be specified on the Saxon command line with -init:ConnectorSaxon9apiInitializer.

Someone who understands Maven better than I do should somehow fix pom.xml so that it's possible to build both forms of Saxon extension at once.

@c-alpha c-alpha mentioned this pull request Nov 2, 2020
Closed
@c-alpha
Copy link
c-alpha commented Nov 2, 2020

It seems that this PR does what the DITA-OT Implementing Saxon extension functions manual describes for Saxon 9, i.e. will make xslthl usable in a DITA-OT plugin again?

@tgraham-antenna
Copy link
Contributor Author

It works well enough for me where I run Saxon on the command line. YMMV.

This PR probably should not be merged as-is because it stops the existing SaxonB version from building.

I am not familiar with the DITA-OT technique of using <service> elements in an Ant build file, so I can't say how this PR relates to that technique.

@c-alpha
Copy link
c-alpha commented Nov 2, 2020

[...]
This PR probably should not be merged as-is because it stops the existing SaxonB version from building.
[...]

http://saxon.sourceforge.net Saxon B is officially in "deep freeze" state, so I would speculate that the number of users affected by removing support for it will likely be very limited.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
53A5
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@tgraham-antenna @c-alpha
0