[tdf-discuss] Re: A better idea for a download package.
Hi Carl, Leif , all
Carl Symons wrote:
On Tue, Nov 30, 2010 at 12:10 PM, leif <firstname.lastname@example.org> wrote:
Den 30-11-2010 11:43, plino skrev:
The point here is that OOo has a small installer with 140Mb (no Java, and
only English, Spanish and French dictionaries).
Why is LO going in the opposite direction with 299 and 466Mb???
Agree. This is a problem
I think that an English only version of LibreOffice and then separate
Language Packs (10-40Mb) which include the translation for the interface and
dictionaries, spelling, etc is the best option.
No no no no no no!
If you think all people on this planet are native English speaking you
are wrong. Please. We have discussed this so many times that I don't
believe we still are.
English installer + native lang-pack is a no-go!
At least if this combination is the only one we offer.
Non-English speaking people need installers in their own language.
Even if it is better to have an English installer with the ability to switch later to
the native language, the goal must be to provide every user with an application
she can install and use without language bariers.
But for the sake of bandwidth, a modular installer might not only serve for the
points already mentioned by others.
My idea would be a download manager and installer working together seamlessly:
On download people should be asked for their language at first (or guessed from
the browser with the possibility to switch the download manager language).
Then the download manager provides two options:
- single step download of core application, language pack and main (5?) extensions
in the detected language and for the detected operating system.
- customized download for different application and language packs, extensions,
templates, graphics and so on.
Before downloading them, the selected modules are integrated in a single packet
that can be handled as a single file afterwards (self extraction or something similar).
In this packet an automatically generated file will be added
containing the modules selected and downloaded.
After downloading the package installation process can be started by clicking on the
package: The installer will pick the appropriate language from the content file and start
in this language. Installation of the core program will be done like today, but the
installer must be translated outside the program, so it can be replaced easily.
As a second step inside the installer the language pack will be installed immediately
afterwards. In this case the download is the smallest possible (core + 1 lang-pack),
while the user will not perceive that there have been two downloads.
She just starts LibreOffice in her language.
Depending on the modules selected on download the installer allows to install all of
them at once or to choose the modules to be installed manually.
In this way different lang-packages can be integrated in the suite while keeping the
installer GUI in the user's native language.
This idea would need some development skills to become a valid option for LibreOffice.
But I think it could be worth while. Perhaps others too?
Could we find a developer interested in this area?
PS: I wanted to sketch a draft containing all the different options for download and install
I mentioned here. Unfortunately I can't use Draw to create this draft and upload it because
here at work there are several restrictions....
Unsubscribe instructions: E-mail to email@example.com
*** All posts to this list are publicly archived for eternity ***
Impressum (Legal Info)
: 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