-
-
Notifications
You must be signed in to change notification settings - Fork 268
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
Add help from welcome.htm content #231
Comments
For the following keyboards for keymanapp#231: * indic roman transliteration * inuktitut_4 * khowar * km_cree * km_ojibwasyllabics * km_ojicreesyllabics * kmhmu * korda * korean_morse
For the following keyboards for keymanapp#231: * thompsonu * tunesianspokenarabic * turkmen * urdu ph - package * waiwai * wiwa
For the following keyboards for keymanapp#231: * thompsonu * tunesianspokenarabic * turkmen * urdu ph - package * waiwai * wiwa
see issue #237 |
The remaining ones where we do have sufficient documentation to create help files are: |
gff_ethiopic_7 doesn't have good documentation so I cannot do it or gff_amh_powerpack_7 becaise the powerpack depends on gff_ethiopic_7 documentation. We did not create help files for the deprecated Windows Basic keyboards. I believe all the help files we can do are done. |
Many keyboards are missing online help documentation, but the .kmp files contain
welcome.htm
content that can be used.Running a script, the list seems to be:
Legacy Keyboards
[ ] ./legacy/p/phonyrus/source/phonyrus.kmpAlready exists[ ] ./legacy/v/venetian/source/venetian.kmpAlready existsRelease Keyboards
[ ] ./release/sil/sil_ipa/build/sil_ipa.kmpAdded in #207Questions
For keyboards that contain
welcome.htm
in the .kmp file, convert them tohelp/[keyboardID].php
so they'll deploy to help.keyman.comThe text was updated successfully, but these errors were encountered: