-
-
Notifications
You must be signed in to change notification settings - Fork 118
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 Piedmontese language #748
Conversation
So e.g. in the language settings, the displayed name is
Additional languages basically do not add any relevant load or size, so even uncommon languages are welcome (Kaitag has even less speakers than Piedmontese).
Sure, you're welcome to add it there! |
Ok that gets tricky, it does work fine in Italian, English and French, but it only shows pms in Spanish.
Perfect, let's carry on then! (That's interesting, wonder how doesn't it qualify as endangered, but that's a question for another day..)
Great, will do. Do I use the experimental folders? |
This is a really weird situation... I had not expected something like that. Detecting that display name is the same as language code is easy, a fall back to English should not be hard to implement.
That's your choice. I usually add the ones I create to the experimantal folder because my scripts to create them seem to have issues, and the dictionaries contain some unwanted words. |
I am running android 14 (lineageos 21), not sure if it would make sense to test this on different versions, I don't have access to older devices.. |
Could you try changing + val localeDisplayName = locale.getDisplayName(context.resources.configuration.locale())
+ return if (localeDisplayName == languageTag)
+ locale.displayName
+ else localeDisplayName
- return locale.getDisplayName(context.resources.configuration.locale()) at the end of |
related changes done in separate commit
Ugh, this is really horrible to deal with. |
Yeah neater out of this PR, thanks for merging and working on it! |
This PR adds support for Piedmontese.
Considering it's using latin script, the name is displayed by android and no new layout is needed, I hope I'm not missing any modification (tested locally and seems to work fine).
I didn't find any information regarding how common a language should be to be included in the keyboard, this language is definitely not common (but present on Gboard and swipe, for instance), is it alright to include support relying on a downloadable dictionary? I'll create a follow-up PR in https://codeberg.org/Helium314/aosp-dictionaries