Skip to content

Nyangatom Keyboard - #4062

Open
asnakeberhanu wants to merge 6 commits into
keymanapp:masterfrom
asnakeberhanu:master
Open

Nyangatom Keyboard#4062
asnakeberhanu wants to merge 6 commits into
keymanapp:masterfrom
asnakeberhanu:master

Conversation

@asnakeberhanu

Copy link
Copy Markdown

This is Nyangatom Keyboard

@keyman-server

Copy link
Copy Markdown
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.

@LornaSIL

Copy link
Copy Markdown
Contributor

Thanks for your pull request. As a first time submitter, there are some things you will need to do to make this acceptable.

First of all, please read the readme here: https://github.com/keymanapp/keyboards#file-layout

Also, read this page: https://help.keyman.com/developer/current-version/reference/file-layout

Your own files will need the folder and filenames renamed and moved to keyboards/experiemental/n/nyangatom.
For example,

  • rename the folder to: nyangatom
  • rename all the files
  • Nyangatom.php.text to nyangatom.php (delete the extension .text)
  • Nyangatom.kmn to nyangatom.kmn
  • Nyangatom.kvks to nyangatom.kvks
  • Nyangatom.kps to nyangatom.kps
  • Nyangatom.keyman-touch-layout to nyangatom.keyman-touch-layout
  • Nyangatom.png to nyangatom.png

Delete:

  • LICENSE (leave LICENSE.md)
  • Nyangatom.kmx
  • Nyangatom.js
  • Nyangatom.kpj.user (that's a temporary file)
  • yangap_phone.kpj and yangap_phone.kpj.user (these seem to be from another keyboard.)

You've made changes to other files in the root of the repo, that should not be modified. It might be best to start with a clean repo. In the end, you should have a folder structure like this:

keyboards/experimental/n/nyangatom
│   HISTORY.md
│   LICENSE.md
│   README.md
│   nyangatom.kpj
│
└───source
        nyangatom.ico
        nyangatom.keyman-touch-layout
        nyangatom.kmn
        nyangatom.kps
        nyangatom.kvks
        nyangatom.png
        readme.htm
        welcome.htm
└───source/help 
          nyangatom.php

Please do not submit any of the files in the build folder which would be the compile files.
Once the files are in the correct location I can check the keyboard itself.

@LornaSIL

Copy link
Copy Markdown
Contributor

@asnakeberhanu do you need help with doing these things?

@LornaSIL

LornaSIL commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

At this point you have the files in the correct location in experimental. However, you still have all the extra files from before which are in the root of the repo. The changes in the root need reverting and the folder called Nyangatom Keyboard and the file called yangap_phone.kpj needs removing. Other files you've added or modified need fixing.

It would be best to start with a clean pull request (making sure your repo doesn't have these changes since you are working in master) and then add the files into experimental.

There are some issues with the keyboard in experimental.

  • The LICENSE.md file needs the license string to be: Copyright © 2026 SIL Ethiopia (add the word "Copyright" and the year). Otherwise our build system won't work.
  • In the .kmn you say the targets are "any", but you only have rules for touch. We do allow touch-only keyboards in experimental, but our preference is that you include a desktop layout so that if someone connects an external keyboard to a tablet, they can use the keyboard. You would need to add rules for the epsilon and open o. RALT+e and RALT+o would be easy to add, plus the shift ones.
    • Now, I see that the .kmn file in Nyangatom Keyboard has the rules you need. So, you need to make sure all your files are updated in experimental/n/nyangatom and that that keyboard works as you want it.
  • If you keep the targets to "any" you should add those desktop rules and then you can fill in the OSK. To do that, go to the On-Screen tab, select "Auto-fill underlying layout" and then click on "Fill from layout". Do this after adding the rules.
  • If you don't want to add desktop rules, then you need to make the targets just be "mobile".

If you need help figuring this out, let me know.

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