[Libreoffice-bugs] [Bug 89657] The lang-pack installation mechanism on OS X unacceptable -- needs refactoring for better installation UX
bugzilla-daemon at bugs.documentfoundation.org
bugzilla-daemon at bugs.documentfoundation.org
Thu Sep 14 11:31:08 UTC 2017
https://bugs.documentfoundation.org/show_bug.cgi?id=89657
--- Comment #63 from Fred <d1312 at phx.li> ---
OK, so the "start LO once before updating" issue is now solved and automated
(cool), but the key problem is left unaddressed: the process to install a
non-US variant (i.e. core + langpack) is not end-user compatible (i.e. simple).
To repeat myself:
> Assuming the need to start up LO once before a langpack is installed is fixed,
(which is apparently the case if I read the script)
> the easiest way to fix this would be for the langpack to have an option
> "set LO interface language to xx" and enable this by default.
> So, if I were to install in German, the langpack would show a screen in
> German (or maybe both English and German to keep it universal)
(where "German" is any value of $LangpackLanguage)
> and a tickbox already ticked that states "set LO default interface to
> Deutsch/German". It still means you have two stages in install (LO +
> langpack) but it omits the third stage where you have to dig out where
> the language settings are hiding and do the very thing you'd install a
> language pack for in the first place.
In a nutshell, without this, a non_US LO installation is not really user
upgradeable as it doesn't speak the user's installed or desired language.
Thinking about this some more, the langpack itself could actually be the
overall installer (so you have just one language to manage during the install
process), or the LO installer could have a feature to download the right
langpack as part of the process (which is more costly in that you then need all
languages in the installer).
Whatever approach is taken, what matters is that during that install process,
LO is already set up to use the UI contained in the langpack, instead of the
user having to start it up in English and then dig through the settings to
finally set the LO UI in the language of the langpack, exit and restart. Since
you have all the data to hand when you start a langpack, why not use it, or
default to using it and offer the user an ability to opt out (just in case)?
The goal is to improve the install process to the point where a non-English end
user can do this in one single go without ever having to switch away from their
own language.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20170914/eb90f843/attachment.html>
More information about the Libreoffice-bugs
mailing list