Skip to content

Storing detected languages #66

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

Closed
jmokoistinen opened this issue Sep 2, 2020 · 14 comments · Fixed by #77
Closed

Storing detected languages #66

jmokoistinen opened this issue Sep 2, 2020 · 14 comments · Fixed by #77
Milestone

Comments

@jmokoistinen
Copy link

jmokoistinen commented Sep 2, 2020

Hi,

Wondering which would be best way to store information of detected language(s) and their point difference. The information is to be used by UI to filter pages by their language(s).

@jukervin commented that possibly currently only way is to use Page element QUALITY_DETAIL attribute (string)

Any other ideas? Thanks!

@jukervin
Copy link
Member

jukervin commented Sep 2, 2020

I didn't see a proper / elegant way to store the information within the schema.

  • Processing doesn't have a element to record processing outcome information or note. Information would have to be stored in processingStepDescription or processingStepSettings.
  • Page or PrintSpace/Margins don't have TAGREFS for using OtherTag and the information would need to apply to whole page.
  • LANG (xsd:language) is available in TextBlocks and below and can only store one language without additional information.

@artunit
Copy link
Member

artunit commented Sep 27, 2020

@bertsky's comment on Add LANG and ROTATION attributes to Page element might be considered here. PAGE uses xsd:list itemType="xsd:language" to allow a comma-delimited list, and this approach could be considered for ALTO.

@cipriandinu cipriandinu added this to the v4.4 milestone Apr 15, 2022
@cipriandinu cipriandinu linked a pull request Apr 15, 2022 that will close this issue
@cipriandinu
Copy link
Member

ACCEPT

11 similar comments
@cneud
Copy link
Member

cneud commented May 3, 2022

ACCEPT

@ntra00
Copy link
Member

ntra00 commented May 3, 2022

ACCEPT

@Haighton
Copy link

Haighton commented May 4, 2022

ACCEPT

@acpopat
Copy link
Member

acpopat commented May 4, 2022

ACCEPT

@jukervin
Copy link
Member

jukervin commented Oct 6, 2022

ACCEPT

@cowboyMontana
Copy link
Member

ACCEPT

@callylaw
Copy link
Member

callylaw commented Oct 6, 2022

ACCEPT

@JLoitzenbauer-CRKN
Copy link

ACCEPT

@cowboyMontana
Copy link
Member

ACCEPT

@c-sebastien
Copy link

ACCEPT

@cowboyMontana
Copy link
Member

ACCEPT

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.