Current implementation of Impress Remote on iOS does not offer selection of UI language in settings - this way only iOS supported languages are allowed which dramatically cuts down the LO supported languages list.
Many apps for iOS have an internal setting to set interface language that overrides the system set language in iOS. This way these apps allow communication with users in languages not supported by Apple.
IMHO, in the spirit of values of TDF and the LO project this should also be the case with the iOS remote app. Let me also emphasize - this is a very important issue for language communities with languages not supported by Apple/iOS.
Since there is no 'iOS Impress Remote' I set the component to 'Android Impress Remote', maybe such a component should be added as well.
Set to New , I've ask for the component to be added on the QA list- Sophie
This also needs to be implemented for Android. I just upgraded, as of 4.2 (see screenshot) Android no longer allows Custom Locale apps so users are stuck with the default system locale.
Created attachment 105029 [details]
Android 4.2 error message
@Michael: Please file another bug report. It's annoying when people stack multiple issues in an existing report, causing that you can never close it. This one was specifically about iOS, and not a meta bug.
No need to get so angry. I'm not a developer, I'm a localizer. I don't know how exactly these things work but it did not seem far-fetched that adding a menu item to iOS would involve the same process as doing it for Android.
I was just trying to save folk time by not having to deal with another bug but if we need to file different bugs for the same thing on iOS and Android then I will.
(In reply to comment #5)
> No need to get so angry. I'm not a developer, I'm a localizer. I don't know
> how exactly these things work but it did not seem far-fetched that adding a
> menu item to iOS would involve the same process as doing it for Android.
> I was just trying to save folk time by not having to deal with another bug
> but if we need to file different bugs for the same thing on iOS and Android
> then I will.
The code for the two platforms is _completely_ separate, and hence a very
different process for each -- it is unlikely that people with iOS skills would
have the appropriate Android skills to do this (and even if this were the case, they wouldn't be developing both concurrently), and hence separate bug reports would be much more appropriate.
(However tbh. I don't see why we should be compensating for deficiencies in Operating Systems, and on Android at least I haven't ever seen language selection being part of an App.)
Ok I will file another bug.
>(However tbh. I don't see why we should be compensating for deficiencies in
> Operating Systems, and on Android at least I haven't ever seen language
> selection being part of an App.)
Well, lucky you for being a speaker of a large nation-state language which is supported by Android. My guess is, you haven't looked too hard. Just FYI, Mozilla has just implemented exactly such a feature for exactly those reasons
Moving bug to (new) 'Impress Remote' product.