[Libreoffice-ux-advise] [Bug 113119] Customize/personalize windows installer to user' s download preference

https://bugs.documentfoundation.org/show_bug.cgi?id=113119

Mike Kaganski <mikekaganski@hotmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #2 from Mike Kaganski <mikekaganski@hotmail.com> ---
The current MSI architecture was introduced in 3.5 [1] just to go away from old
EXE+MSI+Languages+stuff. Launching installer in system's (actually user's)
language (concern a) is normal, because if user can use system with this
language, then there shouldn't be problems with understanding the installer's
messages. Trying to do otherwise would fail in case a system doesn't have
support for e.g. arabic (or other language). Moreover, if that is a multi-user
system, and the arabic-language installer would succeed, then later
non-arabic-speaking person could have troubles with reconfiguration or
uninstall.

The same is also true for default UI language and locale (concerns b and c).
Given that there is a possibility that LO would be used in multi-language
environment, having single-language installers would also make it more
difficult to support such scenarios where one system is used by
different-language-speaking users, and correct solution in this case is to have
proper user UI language selected on OS level (e.g., using MUI packs on
Windows).

While there *could* be users whose experience would increase from the proposed
changes, the downside for many others would greatly outweigh this. The
maintenance cost (both in terms of developers' effort, and of user support
required to solve problems resulting from this change) would increase
non-proportionally.

Closing WONTFIX.

[1] https://wiki.documentfoundation.org/ReleaseNotes/3.5#Windows_installer

-- 
You are receiving this mail because:
You are on the CC list for the bug.