-
Notifications
You must be signed in to change notification settings - Fork 12
Can Hudum hypenation points be derived from Cyrillic? #43
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
Comments
In order to wrap part of a Hudum word into the next line (not even talking about hyphenation), the layout engine needs to be able to break the word after shaping the whole word. Is that already solved? |
That has been requested, but first the browser needs to be able to identify potential break points. Then it can check that the hyphenation rendering is typographically correct. So my question still stands: can Gecko generate a set of hyphenation break point rules for Hudum from the Cyrillic rules? |
I’m just here to make sure you understand that it’s not a matter of being “typographically correct”, but orthographically correct. Breaking a Hudum word before OTL leads to entirely wrong spellings. |
From my research, while Cyrillic Mongolian hyphenation rules provide a useful foundation, directly generating traditional Mongolian hyphenation rules from them is not straightforward due to differences in script structure, directionality, and syllabic boundaries. However, aligning corresponding morphemes between the scripts could offer a pathway to semi-automated rule generation with linguistic validation. |
So i think we have the (not unexpected) answer: No. Thanks. |
I raised a set of issues for Gecko, Blink, & Webkit browsers requesting better support for hyphenation in Mongolian.
Gecko folks noted that they don't have hyphenation break point rules for traditional Mongolian script, but they do for Mongolian written in Cyrillic. They asked the question: would it be possible to automatically generate hyphenation rules for traditional from the cyrillic one?
Any thoughts?
The text was updated successfully, but these errors were encountered: