Kazakh layout is missing
Maintainers usually reply within 5 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
The payload names no source files, so start by finding how existing language layouts are defined and registered in the Kotlin Android keyboard code. The attached screenshot is the only source for the key arrangement, with the special letters placed on the top row, and the latin-based variant is optional. Done means a Kazakh layout is selectable in the app with the special letters on top, and the existing layout tests still pass.
Written by the indexing model from the issue text.
Description
Checklist
- I made sure that there are no existing issues - open or closed - to which I could contribute my information.
- I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
- I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
- I have taken the time to fill in all the required details. I understand that the request will be dismissed otherwise.
- This issue contains only one feature request.
- I have read and understood the contribution guidelines.
Feature description
Kazakh layout should be included in the app.
Why do you want this feature?
Because it is my native language and I need to use it for communication.
Additional information
To make it easier to use the layout, all special letters should be on top as seen on the attached screenshot. Optionally, a layout with the new latin-based script should also be included.
- Dominant language
- Kotlin
- Stars
- 678
- Forks
- 84
- Avg merge
- 5d 9h
- Merged PRs (30d)
- 8
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from FossifyOrg/Keyboard
-
Error of the Ukrainian keyboard layoutPossibly taken A pull request linked to this issue is open or already merged. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
FossifyOrg/Keyboard#487 · 1 comment ·
Maintainers usually reply within 5 days
-
bug needs triage
Difficulty 4/5 3-5 days Newbie friendliness 48/100
FossifyOrg/Keyboard#484 ·
Maintainers usually reply within 5 days
-
bug needs triage
Difficulty 3/5 1-2 days Newbie friendliness 35/100
FossifyOrg/Keyboard#462 · 1 comment ·
Maintainers usually reply within 5 days
-
bug needs triage
Difficulty 4/5 3-5 days Newbie friendliness 18/100
FossifyOrg/Keyboard#450 ·
Maintainers usually reply within 5 days
-
feature request needs triage
Difficulty 3/5 1-2 days Newbie friendliness 35/100
FossifyOrg/Keyboard#447 ·
Maintainers usually reply within 5 days
All issues in FossifyOrg/Keyboard
Similar issues
-
bugbane/qf good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
osservatorionessuno/bugbane#173 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Bayern feature:Application ready web
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
digitalfabrik/entitlementcard#3176 ·
Maintainers usually reply within 7 days
-
bug need-device
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
ramesh130/superplayer#495 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
maxrave-dev/SimpMusic#2649 ·
Maintainers usually reply within 2 days