With the phone set to english, many languages are just appearing as squares [][][][], which doesn't really look very good...
Version: 1.0.0 (Android)
Severity: enhancement
Description
Description
Details
Details
- Reference
- bz32007
| Title | Reference | Author | Source Branch | Dest Branch | |
|---|---|---|---|---|---|
| [build.start]: default to tailing build logs on start | repos/cloud/toolforge/builds-cli!13 | raymond-ndibe | build_start_default_to_log_follow | main | |
| [builds-cli]: drop direct k8s api calls and use builds-api exclusively | repos/cloud/toolforge/builds-cli!6 | raymond-ndibe | full_frontend_refactor | main |
| 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 | • brooke | T35208 Switch "near me" from Google Maps Android API to HTML-based OpenStreetMap backend | |||
| Invalid | None | T35855 Wikipedia Android App potential features (tracking) | |||
| Resolved | None | T34007 Many language names are in unsupported encodings/fonts |
Event Timeline
Comment Actions
It should be possible to ship some additional fonts with the app or just let webfonts do their work (-> general 'support webfonts in MobileFrontend'?)
Note however that not all scripts will render correctly even if fonts are provided. There's improved support for Indic scripts in Android 3 or 4 though.
Comment Actions
Extra web fonts wont do us any good if Android has no rendering support for them. So we can either shame android and show its poor language support or maintain a list of what works where. Thoughts?
Comment Actions
Presumably, if it's not showing in a language, it's not going to show in any language? ie Android doesn't have support for that language?
Similarily, will that language work in the browser, or is it just Android itself with the lacking support?
It'd feel a bit bad blacklisting languages completely if they have partial support. If they are completely unsupported, it isn't so bad.
Maybe we could do "LocalLanguageName (Canonical/EnglishLanguageName)" too?
Or to keep it more like MediaWiki "langcode - LocalLanguageName"
Comment Actions
philinje wrote:
A good usability enhancement would be to show the name of the language, even if it's not supported, as Sam suggested with LocalLanguageName. And then gray it out to show the language is not being rendered.
Presumably, this is the same as the language not being supported on that device, and therefore all apps on that device would have the same problem. But there must be a way to check the available languages, right?
This is tricky because I know on some devices the available languages for the phone is not the same as what languages will be rendered.