Conversation
Member
Author
|
See related issue #124. |
This avoids problems with other installations which might miss the required models. Signed-off-by: Stefan Weil <sw@weilnetz.de>
Signed-off-by: Stefan Weil <sw@weilnetz.de>
Signed-off-by: Stefan Weil <sw@weilnetz.de>
Member
Author
|
Meanwhile there is a newer 10.8 (released 2022-03-15), so I updated the pull request. Can we merge? There is also a new major release 11: "Saxon 11.3 is the latest release for production use; however for critical applications using SaxonJ Should we skip release 10 and go directly from 9 to 11? |
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The new stable version 10 no longer has a patch version and uses a different naming convention for the .jar file. Therefore ocr-fileformat now always uses a symbolic link
saxon.jarwhich links to the installed .jar file.Make also the round trip test a little bit more stable by running
tesseractwith an explicit path. The round trip test shows some differences between initial and final ALTO file, but those differences look acceptable.