adapt to ocrd v3 #69
Open
adapt to ocrd v3 #69
Conversation
This file contains 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
…orydict default (keeping special case source=PAGE)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
attempt at migration towards OCR-D/core#1240
no tests yet, I will try to add some CI here
@kba see
ocrd_segment.replace_originalfor the use case of passingPageTypeinOcrdPageResultImage.images.alternative_image. – It pairs with the complementaryocrd_segment.replace_page, so one can use replace-original to rebase, then run a few steps, and then use replace-page with the result as second fileGrp and the original fileGrp as second fileGrp to continue with the results (all annotation below page level) in the original coordinate system.