Re: [Libreoffice] The Windows installer

On 10/14/2010 12:00 PM, Tor Lillqvist wrote:
> > I see that it's an installer that includes all the languages but i
> > wonder if it is really necessary and if the languages are the only
> > cause.
>
> Well, there certainly isn't hundreds (or even tens) of megabytes of
> new code, as far as I know, so yes, it must be the languages.

Clearly it's not code. I thought about debugging symbols or something 
that went wrong during compilation or that got erroneously included in 
the final archive.

> Of course, this
> is supposed to be a meritocracy, I think, so if you have actual
> experience in building and packaging OOo or LO installers, that gives
> you more clout.

I'm not a developer, just a user and i'm trying to help filing bug 
report, testing your beta releases and discussing like now to make 
LibreOffice better.
I really appreciate this open approach.

> Sorry, but I think that is against the Document Foundation's "Next
> Decade Manifesto", which says: "WE REJECT: [...] the creeping
> domination of computer desktops by a single language forcing people
> to learn a foreign language before they can express themselves
> electronically"

When i wrote the message i didn't read the manifesto. I understand your 
point.

> OK, so if an *installer* could be multi-lingual even if it installs
> just the English UI, what you say could be a viable approach.
> Currently that is not possible, as far as I know, but it should be
> possible to do it that way using some amount of work on the Perl code
> that directs the installer generation. Something to discuss, sure.

In my opinion:

* 320 MB for an installer is too much. If you don't have a fast internet 
access or if you have a mobile provider that gives you time/data limit, 
probably you'd have to find another way to get LibreOffice.

* An unique installer that include all the languages is a really good 
idea if we are able to find a way to reduce its size to saner value. Up 
to then, i find more viable the approach of providing separate installer 
for each language. This is something to which OOo users are already 
comfortable with. And i think that also in this case the installer is 
already big enough!  ;-)

* A multi-lingual installer, as you said, that include only a single 
language has some options:
- the localized build is integrated, and so you are again in the OOo 
default, where you have to download an installer for the language you want.
- the installer is only the installer and doesn't include the LO 
archive. In that case you have to find a way to obtain it: the installer 
can download it (i don't really like that options, since makes life more 
difficult for administrators), or the user have to manually download 
both the installer and the localized LO build (similar, but inversed 
go-oo approach).

For now i'd stay with the OOo default (and many other projects default) 
to have one installer for one language.
Just my opinion.

Ciao.

Cesare.