-
Notifications
You must be signed in to change notification settings - Fork 51
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
Could we get Southern Altai support? #432
Comments
As to hyphenation I suggest you wait until @reutenauer is back; he can definitely give you some guide. With regard to the gloss file, I suggest you take one that is most closely to Southern Altai as a model and begin to integrate things (captions etc.) there. Since Altai uses multiple scripts, maybe |
That is probably a good suggestion. I assume you read the Wikipedia page (which is the best English source on anything on the language,) so I shan't say more than is necessary, but they really only have used two scripts Latin and Cyrillic, but of course custom variants. I shall get on that, thank you. |
I have created a base file that I am ready to test, how would I go about doing that? (it is still along way away from being ready for a commit.) Edit: NVM, lol, I forgot that putting it in |
I love the
polyglossia
package (obviously) and I have a niche usage for it; I need to be able to easily typeset an obscure Turkic language I am trying to learn. I don't expect anyone who actually is working on it to go through all that trouble, but I was hoping I could write some basic hyphenation files, etc. and do a pull request in the future.I am going to try and write my own package
*.ldf
(gloss-alt.ldf
), etc., regardless, but I would like to ask if I could be given some general pointers in how to do it apropriately, smoothly. I am looking, now, and the Russian and English packages as a guideline. I don't intend on writing ababel
package if I don't have to. I am typesetting a New Testament, so I should be able to produce a fairly thorough hyphenation package, etc. within a year or so.The text was updated successfully, but these errors were encountered: