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

SLP1 - Roman keyboard #3266

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

Harshavardhan-Pandurangan

The Sanskrit Library Phonetic ASCII package includes two keyboards: one to enter Devanagari Unicode, the other to enter Roman Unicode with diacritics. These include all accents required for The R̥gveda. Both keymaps follow the Sanskrit Library ASCII encoding described in brief at https://sanskritlibrary.org/help-text.html, and in full in Linguistic Issues in Encoding Sanskrit, Appendix B available in a PDF linked to at the bottom of that webpage. The Romanization followed in the slp1_roman keyboard is ISO 15919 except e and o are represented as in IAST without the macron. Capital characters are obtained by wrapping the character sequence in curly brackets.

The Sanskrit Library Phonetic ASCII package includes two keyboards: one to enter Devanagari Unicode, the other to enter Roman Unicode with diacritics.  These include all accents required for The R̥gveda.  Both keymaps follow the Sanskrit Library ASCII encoding described in brief at https://sanskritlibrary.org/help-text.html, and in full in Linguistic Issues in Encoding Sanskrit, Appendix B available in a PDF linked to at the bottom of that webpage.  The Romanization followed in the slp1_roman keyboard is ISO 15919 except e and o are represented as in IAST without the macron.  Capital characters are obtained by wrapping the character sequence in curly brackets.
The Sanskrit Library Phonetic ASCII package includes two keyboards: one to enter Devanagari Unicode, the other to enter Roman Unicode with diacritics.  These include all accents required for The R̥gveda.  Both keymaps follow the Sanskrit Library ASCII encoding described in brief at https://sanskritlibrary.org/help-text.html, and in full in Linguistic Issues in Encoding Sanskrit, Appendix B available in a PDF linked to at the bottom of that webpage.  The Romanization followed in the slp1_roman keyboard is ISO 15919 except e and o are represented as in IAST without the macron.  Capital characters are obtained by wrapping the character sequence in curly brackets.
@keyman-server
Copy link
Collaborator

Thank you for your pull request. You'll see a "build failed" message until the Keyman team has reviewed the pull request and manually initiated the build process.

Every change committed to this branch will become part of this pull request. When you have finished submitting files and are ready for the Keyman team to review this pull request, please post a "Ready for review" comment.

PLEASE NOTE: team capacity for review is limited in December 2024 and will resume in January 2025. We appreciate your patience.

@LornaSIL
Copy link
Contributor

LornaSIL commented Jan 6, 2025

This pull request is in better shape than your previous one. I haven't done a thorough check, but these are the issues I can see immediately.

  • if you could remove the version number from the README.md file then that file won't need to constantly be updated. It is sufficient to include the version in the HISTORY.md file and in the .kmn file
  • The .kvks file is empty. When you open the .kmn file and go to On-screen keyboard tab you can import the on-screen keyboard. That will make it more useful for your users. Otherwise the OSK will be blank.
  • We do not allow distribution of proprietary fonts. That means that the times.ttf font may not be distributed here. It is a Monotype font with a restricted license. You'll need to remove the font and change the font in the .kps.
  • The Sanskrit2020.ttf font is allowable because it appears to be under the Open Font License. However, we do not wish to have a lot of different font files with the same name in our repo, so when a font seems like it will be useful for several different keyboards, we prefer to add them to our release\shared\fonts section of the repo and then it can be used for various keyboards. I'll go ahead and add it there. When that's done I'll suggest what to do next.

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

Successfully merging this pull request may close these issues.

3 participants