Date: prev next · Thread: first prev next last
October 2017 Archives by date, by thread · List index


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

--- Comment #12 from Mike Kaganski <mikekaganski@hotmail.com> ---
The recurring questions on AskLibO that keep asking why a help pack doesn't
work suggest that having different installers for different languages bring
more confusion than help.

The problem with help packs not working is that users use one UI language, but
have help pack from another. They don't find it intuitive to match UI language
and help pack language; the hypothetical one-helppacks-in-one-installer
scenario would solve great number of user problems. Of course, at cost of
increased download size.

The reduced size of program installer wouldn't be that small as to help people
to go from 4 hrs of download to 15 minutes. More realistic is scenario when
this will reduce to ~3 hrs; and that would still make most people who refuse to
download now to keep refusing. But the cost will be great, both in terms of
developers effort, infrastructure (size required for each version on servers),
and user support in cases like where a single-regional setup is tried to be
upgraded by all-lang installer (waste of bandwidth again, because user now
needs to re-download required package?) or other interesting issues.

My strong opinion is WONTFIX.

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

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.