Arabic letters placement and layout is different from gboard

Offen
  • Stimmt etwas nicht?
#201 2 Kommentare 1 Reaktion 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
15/100
Issue-Typ
Feature
Klarheit
Muss geklärt werden
Aktivitätsstatus
Veraltet
Tech-Stack
android, kotlin
Bereich
mobile

Rechercherichtung

The payload names no files, tests or entry points, so start by finding where the Arabic key layout is defined in the Kotlin Android keyboard code. Then compare it with a reference Gboard Arabic layout to pin down which keys move. Done means the layout matches a specific, agreed reference, which the issue does not yet define, so confirm the target with a maintainer first.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

feature request l10n needs triage
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

Aeabic languge letters follow differnet scheme that gboard

Why do you want this feature?

I currently switched from gboard as a lot of people will do but the arrangements of the arabic letters makes it uncomfortable to use and needs learning curve. Would be better if it can follow the same layout as gboard to be easy migration thank you

Additional information

No response

Vorherrschende Sprache
Kotlin
Sterne
678
Forks
84
Ø Merge
15 Std. 29 Min.
Gemergte PRs (30 T.)
8

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus FossifyOrg/Keyboard

Alle Issues in FossifyOrg/Keyboard

Ähnliche Issues

Weitere Issues zu Kotlin

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.