Issue 102681 - Decouple installer UI languages from product UI languages
Summary: Decouple installer UI languages from product UI languages
Alias: None
Product: Installation
Classification: Application
Component: code (show other issues)
Version: OOo 3.1
Hardware: PC Windows, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2009-06-11 18:54 UTC by tml
Modified: 2013-08-07 15:26 UTC (History)
1 user (show)

See Also:
Issue Type: FEATURE
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description tml 2009-06-11 18:54:01 UTC
It would be nice to be able to create an installer that would offer its UI in
more languages than the UI languages of the OOo + possible language packs that
it contains. (This holds for both an MSI installer and an NSIS wrapper around it.)

This would enable vendors to offer a single core installer (containing OOo with
just the en-US UI) and separate language pack installers with no complaints from
people in locales like Russia where it is common that users don't know English
well enough. It would be useful if that core installer had its own UI in
multiple languages even if it installs an English-only OOo. The expectation
would be that people before running OOo would then install also a suitable
language pack.

I have tried to come up with a patch for this but so far I without full success.
The two orthogonal concepts, set of installer UI languages and set of product UI
languages, seem to be mixed together tightly and used interchangeably throughout
the Perl code.

Assigning to is, presumably the right person for this?
Comment 1 Olaf Felka 2009-06-12 10:22:33 UTC
For all nearly hundred languages??
Comment 2 tml 2009-06-12 11:12:37 UTC
Did I say that the list of installer languages should be fixed? Of course it
would/should be configurable with some new switch to the configure script, for
instance --with-installer-languages. (And if left out, it would work as now.)
Comment 3 2009-06-15 14:05:37 UTC
In the Java GUI Installer, that we offer for OpenOffice with JRE on Unix
platforms, the installer (jar files) is built in cvs module "javainstaller2" and
contains all available languages. 
Windows is more difficult, because for every language a transformation has to be
created, after the localized msi database was created. And at the moment, the
Italian database contains all installer strings in italian, but also the
filenames, the encodings and so on. 
So decoupling installation language from product language is surely a good idea,
but it will require a lot of time.
Comment 4 2009-06-17 11:22:31 UTC
Accepting and setting target OOo 3.x
Comment 5 2009-06-17 11:26:55 UTC