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.

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

Terminology: Glyphs, characters, codepoints #87

Open
kba opened this issue Oct 26, 2016 · 0 comments
Open

Terminology: Glyphs, characters, codepoints #87

kba opened this issue Oct 26, 2016 · 0 comments

Comments

@kba
Copy link
Owner

kba commented Oct 26, 2016

#17 (comment)

None of these are "per-glyph" because "glyph" isn't a uniquely defined
concept independent of font. As far as hOCR is concerned, you need to
output information per codepoint. There is no single correct way of doing
that: it depends on the script, the encoding, and the OCR engine.

For bounding boxes (or cuts) on accented Western scripts, my recommendation
would be: (1) view the whole accented letter as a single glyph, (2) use
normalized unicode with composed characters, (3) if a single glyph
corresponds to multiple codepoints, output a bounding box for the first
codepoint and output empty bounding boxes for the remaining codepoints.

We should define it and s/character/codepoint in the spec.

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

No branches or pull requests

1 participant