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.

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

Feature: Store frame in PAGE Format #15

Open
M3ssman opened this issue Oct 5, 2023 · 0 comments
Open

Feature: Store frame in PAGE Format #15

M3ssman opened this issue Oct 5, 2023 · 0 comments
Assignees
@einspunktnull @M3ssman
Labels
enhancement New feature or request

Comments

@M3ssman
Copy link
Member

M3ssman commented Oct 5, 2023

Description

Currently, if an OCR-frame is grabbed from existing data and stored back, only permits ALTO both as input and output format.

While ALTO input is common and therefore a very reasonable input format, it would ease the usage with other post correction Tools, different from Transcribus expert client, if we can store the OCR-frame also as PAGE XML.

We have to deal with 2 scenarios when saving as PAGE:

  • fit Transcribus custom Page 2013 format
  • fit Page 2019 format used by OCR-D-Tools as well as LAREX

To do so, please add an output format flag --output-format which internally distinguish between page2013 and page2019.

If not set, defaults to recent alto flavor of Tesseract-OCR, which means technically just preserve as provided.
@M3ssman M3ssman added the enhancement New feature or request label Oct 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@einspunktnull einspunktnull

@M3ssman M3ssman

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@einspunktnull @M3ssman