-
Notifications
You must be signed in to change notification settings - Fork 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.
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
Label, Layers and Relation #4
Comments
8c18d4b implements mapping PAGE Layers: I cannot find any mechanism for expressing z-level in ALTO. As for relations I also doubt it can be easily mapped, at least I don't see how :( |
Excellent! I thought just using ALTO's
What about PAGE's
IMHO you could express it as as
From this recommendation it looks like drop-cap relations should be represented via |
I was unsure myself and let @cneud be the tiebreaker :) I don't really know the difference tbh.
I did not realize that ALTO has
👍
Sure, I can have a look. Do you have an example?
Sure, why not. Again, an example would help with testing.
IIUC the example cited is not a relation from drop-cap to region but just tagging that this |
I concur.
Pass (again), sorry. I have grepped through all my PAGE-XML GT resources (which includes various datasets from PRImA), but have not found anything on It's quite expressive: you can have
You're right – it looked more promising at the first glance. So we do need a representation for I would expect:
But with ALTO we already have an explicit white-space model – on the line level. So I guess you could argue keeping a I was curious how TEI converters handle this. Sifting through with https://github.com/cneud/ocr-conversion and https://github.com/altoxml/documentation/wiki/Software …
I cannot believe there is no existing ALTO-TEI converter capable of unwrapping lines and concatenating text into linear sequence (based on reading order and block/paragraph bounaries). 😦
Not sure anymore we strictly need a relation type (see above: probably just a marker for "join-with-next" on various levels)... |
No description provided.
The text was updated successfully, but these errors were encountered: