Skip to content

add poorigbelle keyboard#3958

Closed
zagazagaturtur-svg wants to merge 7 commits into
keymanapp:masterfrom
zagazagaturtur-svg:master
Closed

add poorigbelle keyboard#3958
zagazagaturtur-svg wants to merge 7 commits into
keymanapp:masterfrom
zagazagaturtur-svg:master

Conversation

@zagazagaturtur-svg
Copy link
Copy Markdown
Contributor

@zagazagaturtur-svg zagazagaturtur-svg commented Apr 17, 2026 •
edited
Loading

this is a fur/poorigbellé language we use to speek from darfur i'm developing this language to use in any device phone and pc

@zagazagaturtur-svg
add poorigbelle keyboard
9a5a546 
this is a fur/poorigbellé language we use to speek from darfur
i'm developing this language to use it in any phone and pc
@keyman-server
Copy link
Copy Markdown
Collaborator

keyman-server commented Apr 17, 2026

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.

@zagazagaturtur-svg
Copy link
Copy Markdown
Contributor Author

zagazagaturtur-svg commented Apr 20, 2026

hello keyman teams i hope everything will be good form my language what i came to develope
thanks you evrvody who is helping me

@zagazagaturtur-svg
Copy link
Copy Markdown
Contributor Author

zagazagaturtur-svg commented Apr 20, 2026

hello keyman team ready to review

@LornaSIL
Copy link
Copy Markdown
Contributor

LornaSIL commented Apr 20, 2026

Thank you for your submission. There are quite a few changes which must be made, but that is normal for a first-time submission, so please do not be discouraged. I will list the changes below.

  • Please delete the README.txt from the root of the poorigbelle folder. That file relates to the Noto Sans font and not to the keyboard. I'll suggest a change related to the font later.
  • Any keyboard that goes in our release must have a regular desktop keyboard. That means you either need to create desktop rules in the .kmn or you should move the keyboard to experimental. This is because there are people who will connect an external keyboard to to a mobile device, and in order for them to have a good user experience, they need the desktop keyboard.
  • One you create the desktop rules, you should go to the On-Screen keyboard tab and import the layout from the .kmn. Right now the On-Screen keyboard is blank.
  • I have not tested the mobile keyboard yet.
  • We do not want to have many different versions of fonts in our repo. That would give users a bad experience if different versions of the font are overwritten by different keyboards. That means you should remove the NotoSans-Regular.ttf font from this pull request. In your .kps file you should reference the font in this folder keyboards/tree/master/release/shared/fonts/noto/Latn
  • Any keyboard in the release section should have some documentation. At a minimum the welcome.htm file should say "Users may view the On-Screen keyboard to view the keyboard layout".
  • Any keyboard in the release section should have a help folder within the source folder. It needs to have a file called poorigbelle.php. So, the path would be poorigbelle/source/help/poorigbelle.php. That file could say:
<?php 
  $pagename = 'poorigbelle Keyboard Help';
  $pagetitle = $pagename;
  require_once('header.php');
?>
<p>
  This keyboard is for the fur/poorigbellé language we use to speak from darfur. I'm developing this language to use it in any phone and pc. Users may view the On-Screen keyboard to view the keyboard layout.
</p>
  • Lastly, the compiled files in the build folder should all be removed from this Pull Request. Our build system will automatically build the files from your source file.

I hope you are able to make these changes without too much trouble.

@LornaSIL
Copy link
Copy Markdown
Contributor

LornaSIL commented Apr 24, 2026

There are multiple issues with this Pull Request.

  • The keyboard only supports mobile.
    • You either need to add rules to support desktop, or you need to move the keyboard to experimental.
  • Either way, the files are in the wrong location. The poorigbelle folder must be in the p folder. Here's an example of the folder structure you should be using:
keyboards/experimental/p/poorigbelle/HISTORY.md
keyboards/experimental/p/poorigbelle/LICENSE.md
keyboards/experimental/p/poorigbelle/README.md
keyboards/experimental/p/poorigbelle/poorigbelle.kpj
keyboards/experimental/p/poorigbelle/source/help/poorigbelle.php
keyboards/experimental/p/poorigbelle/source/poorigbelle.kmn
keyboards/experimental/p/poorigbelle/source/poorigbelle.kps
keyboards/experimental/p/poorigbelle/source/poorigbelle.kvks
keyboards/experimental/p/poorigbelle/source/poorigbelle.ico
keyboards/experimental/p/poorigbelle/source/poorigbelle.keyman-touch-layout
keyboards/experimental/p/poorigbelle/source/welcome.htm
keyboards/experimental/p/poorigbelle/source/readme.htm

You'll need to delete the following files:

  • poorigbelle.css
  • poorigbelle.css.txt
  • pooringbell.keyman-touch-layout (that is misspelled and you already have the other file)

Once you get the files in the correct places, please compile the .kmn. There are errors that need resolving. You will see those in the messages window at the bottom of the Keyman Developer window.

After the .kmn compiles correctly, you should open the .kps. You should not include source files like the .kmn, you should include the compiled files. The list of files you should include in the .kps are:

keyboards/experimental/p/poorigbelle/LICENSE.md
keyboards/experimental/p/poorigbelle/build/poorigbelle.js
keyboards/experimental/p/poorigbelle/source/welcome.htm
keyboards/experimental/p/poorigbelle/source/readme.htm

If you decided to update the .kmn file so that it supports desktop, then you should also include:

keyboards/experimental/p/poorigbelle/build/poorigbelle.kmx
keyboards/experimental/p/poorigbelle/build/poorigbelle.kvk

See if you can figure this out. If not, then maybe I can help you restructure everything. Right now it won't build properly either on my computer or the build system because files are in the wrong location.

@zagazagaturtur-svg
Copy link
Copy Markdown
Contributor Author

zagazagaturtur-svg commented Apr 25, 2026 via email

@zagazagaturtur-svg
Copy link
Copy Markdown
Contributor Author

zagazagaturtur-svg commented Apr 25, 2026 via email

@DavidLRowe
Copy link
Copy Markdown
Contributor

DavidLRowe commented Apr 25, 2026

The "poorigbelle" keyboard won't be available on keyman.com until the pull request is approved and merged.

@LornaSIL
Copy link
Copy Markdown
Contributor

LornaSIL commented Apr 27, 2026

Can you tell me what languages you want this keyboard to support? The qaa code isn't very helpful. It would be most helpful if we list all the languages you want this keyboard to support.

Also, you are using two characters that are not considered a pair in Unicode: U+0273 and U+0220. Are you sure those are the characters you want? U+0273 does not have a matching uppercase character. Usually U+0220 goes with U+019E. Computers understand U+019E and U+0220 to be a matching pair.

@zagazagaturtur-svg
Copy link
Copy Markdown
Contributor Author

zagazagaturtur-svg commented Apr 28, 2026 via email

@LornaSIL LornaSIL mentioned this pull request Apr 28, 2026
Merged
@LornaSIL
Copy link
Copy Markdown
Contributor

LornaSIL commented Apr 28, 2026

Replaced by #3970

@LornaSIL LornaSIL closed this Apr 28, 2026
@LornaSIL
Copy link
Copy Markdown
Contributor

LornaSIL commented Apr 30, 2026

Your keyboard is now online! Happy typing! https://keyman.com/keyboards/poorigbelle

@zagazagaturtur-svg
Copy link
Copy Markdown
Contributor Author

zagazagaturtur-svg commented May 1, 2026 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@zagazagaturtur-svg @keyman-server @LornaSIL @DavidLRowe