A number of folks have found it odd that selecting a language doesn't change the localization of the app itself (as it would on the web site). This could be a nice change to make.
We also support more locales than any given Android setup likely does, including those that it doesn't recognize at all (3-letter codes). Allowing folks to select their locale even when it's not available in other things on their phone might be nice!
Version: 1.0.0 (Android)
Severity: normal
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T33805 Wikipedia Android App 1.1 tracking - current bugs | |||
| Resolved | None | T35802 Wikipedia Android app retains GPS access even when it doesn't need it | |||
| Resolved | • brion | T35208 Switch "near me" from Google Maps Android API to HTML-based OpenStreetMap backend | |||
| Invalid | None | T35855 Wikipedia Android App potential features (tracking) | |||
| Declined | None | T35528 Use language selection to override default locale for i18n |
philinje wrote:
Is the app UI entirely dependent on Translatewiki? So if a language is not available as a phone setting, we can still convert the app UI to the degree translations are available?
If so, this is a nice enhancement. It also brings up the question of what happens if the phone language is changed - would the app UI follow and not the Language setting?
All the translations are shipped with the app, so I seen no reason why they couldn't be used with the exception of font availability and rendering issues.
wikimedia.x.0x wrote:
But what if someone wants to search a different WP language edition but _not_ change the language of the app UI?
I'm going to provisionally WONTFIX this, since we're moving towards native apps with native localization and it's not as amenable to this behavior. If it's really wanted we could consider reopening on the new apps though.