Issue 33113 - <sequence_languages> inconsistent
Summary: <sequence_languages> inconsistent
Status: CONFIRMED
Alias: None
Product: Installation
Classification: Application
Component: code (show other issues)
Version: OOo 1.1.2
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-08-17 15:59 UTC by davidfraser
Modified: 2013-07-30 02:14 UTC (History)
2 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description davidfraser 2004-08-17 15:59:55 UTC 
<sequence_languages> is used in the setup script to initialize the
ooSetupLocales value to the correct list of languages.
Even if the list of languages is included in the Installation Languages section,
it only install the main language into the ooSetupLocales section.
I tried manually overriding gid_Configurationitem_Setup_Office_Locales with a
space-separated and comma-separated list of languages but neither seems to work
if one of the language names has a hyphen in it (e.g. en-US)
I will try and provide more details if required.
Comment 1 davidfraser 2004-08-17 16:08:40 UTC 
This should be moved to installation component, unfortunately I cannot do that
now :-(
Comment 2 pavel 2004-08-17 21:03:47 UTC 
do that.
Comment 3 pavel 2004-08-17 21:04:06 UTC 
.
Comment 4 Olaf Felka 2004-08-18 08:19:54 UTC 
of @ is: Please have a look.
Comment 5 ingo.schmidt-rosbiegal 2004-08-18 11:22:10 UTC 
Making a multilingual network installation the setup writes during the
installation process 

<prop oor:name="ooSetupLocales">
 <value>en-US it</value>
</prop>

into the file share/registry/data/org/openoffice/Setup.xcu

I do not see, that something is going wrong.
Comment 6 davidfraser 2004-08-18 15:25:45 UTC 
I have tried to reproduce the exact problem.
If the DefaultLanguage is en-US, and the setup is run in English (by setting the
LOCALE), then the result is that ooSetupLocales is "en-US" and ooLocale is "en-US"
If the DefaultLanguage is en-US, and the setup is run in Afrikaans (by setting
the LOCALE), but English is selected from the list of languages in the
installer, then the result is that ooSetupLocales is "en-US af"
If the DefaultLanguage is en-US, and the setup is run in Afrikaans (by setting
the LOCALE), and Afrikaans is selected from the list of languages, then the
result is that ooSetupLocales is "af" and ooLocale is "en-US"
If the DefaultLanguage is en-US, and the setup is run in Zulu (by setting the
LOCALE), and Afrikaans is selected from the list of languages, then the result
is that ooSetupLocales is "af" and ooLocale is "en-US"

Running the install script (instead of setup) in English also gives
ooSetupLocales="en-US"

So it seems that ooSetupLocales only contains the language setup is run in, and
possibly one other if the LOCALE and the language selected differ (though not
always ; see the Zulu-Afrikaans mix above)

I don't know if this is the intended behaviour but it seems fairly constistent.

Is there any way to make ooSetupLocales contain all the languages that are
defined in the Installation variable Languages?
Comment 7 Rob Weir 2013-07-30 02:14:28 UTC 
Reset assignee on issues not touched by assignee in more than 2000 days.