The number and selection of locales available on Android vary from country to country, manufacturer to manufacturer and even handset to handset. Most locales are (though theoretically part of Android) not on offer. Especially small-to-medium locales are often affected by this.
Because LO has localized products in many small to medium locales (like Irish (ga) or Scottish Gaelic (gd)) force-locale to set the UI language of the Viewer should be complemented by a feature where the end-user can manually set a different locale for the Viewer UI language.
Increasingly, especially open software offers such features for exactly these reasons, e.g. Firefox Mobile, VLC, WordPress.
enhancement, setting to new
(currently the Viewer doesn't ship with any translations)
I didn't think it did but after the problem with getting locale selection into the Remote or indeed VLC or Mozilla Mobile, I wanted to file a bug as soon as possible to put this issue on the radar.
Setting Assignee back to default. Please assign it back to yourself if you're
still working on this issue
*** Bug 98171 has been marked as a duplicate of this bug. ***
Selecting locale is possible in the current version of LibreOffice Android Viewer, therefore closing as WORKSFORME.
There is no locale/UI language selection function in LO Viewer on Android that I can see.
Created attachment 158519 [details]
Screenshot of the language setting in Android Viewer
It's available when you open the top-right menu, then select "Settings", s. attached screenshot, attachment 158519 [details].
What version are you using?
If you're currently using an older one, can you please retest with a daily build from https://dev-builds.libreoffice.org/daily/master/Android-ARM@24-Bytemark-Hosting/ ?
The only thing I see under General is "Experimental Features". I think it's premature to close the bug before the issue is resolved in release. I'll see if I can make time to install a daily build over the next few days.
(In reply to Michael Bauer from comment #10)
Quite likely this rather old version doesn't have the option yet, and unfortunately, there haven't been actual "releases" for quite a while, so the daily build is probably what you'd want for now.
> The only thing I see under General is "Experimental Features". I think it's
> premature to close the bug before the issue is resolved in release. I'll see
> if I can make time to install a daily build over the next few days.
Well, in my understanding, closing bug reports once they have been fixed on master is the standard workflow here...
(and I don't think that Android Viewer had any releases apart from those built from git master, unlike the desktop variants)
If there's no release likely in the near future, that's even more of a reason to keep the bug open for now, even if usual practice might be to close when fixed on master. Otherwise we'll just end up with duplicate bugs which cost everyone a lot more time and effort that keeping this one open for now.
(In reply to Michael Bauer from comment #12)
> If there's no release likely in the near future, that's even more of a
> reason to keep the bug open for now, even if usual practice might be to
> close when fixed on master. Otherwise we'll just end up with duplicate bugs
> which cost everyone a lot more time and effort that keeping this one open
> for now.
Fine for me...
> If there's no release likely in the near future
Who said that? Why don’t y’all ask Cloph instead of (involuntarily) spreading FUD? :)
> closing bug reports once they have been fixed on master is the standard
> workflow here
Indeed. And Bugzilla’s search also allows to look for closed issues. Possible duplicates aren’t a problem.
BTW, this was fixed by core commit 5bf2ec9ed8728a2042e110122ea2b0e4ff55104a. There are only two translations (German and Turkish), because this is not on Weblate. Cloph?
>Who said that? Why don’t y’all ask Cloph instead of (involuntarily) spreading FUD? :)
Cause we're not all plugged in to the matrix? Some of us exist outside the LOniverse...