|
Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
| Summary: | Installation needs to auto-config OOo appropriately for an environment's current locale | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | General | Reporter: | samphan | ||||||
| Component: | code | Assignee: | helge.delfs | ||||||
| Status: | CLOSED FIXED | QA Contact: | issues@framework <issues> | ||||||
| Severity: | Trivial | ||||||||
| Priority: | P3 | CC: | arthit, davidf, hin.stone, issues, jjc, joerg.barfurth, markpeak, nusorn | ||||||
| Version: | 680m79 | Keywords: | oooqa | ||||||
| Target Milestone: | OOo 2.0.1 | ||||||||
| Hardware: | All | ||||||||
| OS: | All | ||||||||
| URL: | http://specs.openoffice.org/g11n/language_selection/42730_48123_Automated_locale_settings_under_Windows.odt | ||||||||
| Issue Type: | FEATURE | Latest Confirmation in: | --- | ||||||
| Developer Difficulty: | --- | ||||||||
| Issue Depends on: | 32939, 48117, 48123 | ||||||||
| Issue Blocks: | 41707 | ||||||||
| Attachments: |
|
||||||||
|
Description
samphan
2005-02-14 13:06:00 UTC
art -> samphan: To make it more general, could you please change the summary to "On machine with X locale, installation needs to be set up appropriately for that locale" or something similar. Thanks. Component -> "Installatoin". Confirmed. Additional configurations that could be set at the installation time: Tools: Options: - OOo: User Data: Country (if it's a country-specific locale, e.g. en_GB) - Load/Save: HTML Compat.: Character set - Language Settings: (all) - Writer: General: Measurement unit - Writer: View: Horizontal/Vertical ruler - Writer: Basic Fonts (all) - Writer/Web: View: Horizontal/Vertical ruler - Writer/Web: View: Measurement unit - Calc: General: Measurement unit - Calc: Calculate: Date - Impress: General: Unit of measurement - Draw: General: Unit of measurement Format: Page: - Page Style: Page: Page format: Format (e.g. A4, Letter, ..) - Page Style: Page: Page format: Text direction (left-to-right, right-to-left (horizonal/vertical)) Others.. - default dictionary for spell checker - default thesaurus - other language resources - default bullet/numbering style related issue, issue 3729 : Easier/automatic setting of default paper size and measurement units related issue, issue 39733 : Support default value for measurement units,paper size,date/number format settings of: This doesn't make sense at installation time. One setting for all user? No matter which locale I have. That's not 'installation'. I think it should read as "One _default_ setting for every new user", user can change any setting later at his/her will. The thing this feature will do is trying to _minimize_ the changes that a user have to do by him/herself. By guessing a logical default setting from user's locale. I think at least, at the installation time, the program do ask for "Country", that's enough to reasonaly guess many things like: currency, measurement units, paper size, date format, and, in some case, language. IMHO some sort of pattern should be buiilt into the installation sets, depending upon the localisation. So that there would not be any need to ask the user for this setting and that, but by default OOo should follow the default settings as per the localisation. If an user wants to customise the settings, it is fine. These changes could be taken only as user-specific and not general. As far as the installation sets are locale-specific and not general for OOo there would not be any need to ask for the 'Country'. OOo seems to (very) partially do this already. With m87 on Windows XP SP2, if I install on a machine with a US locale, CTL is not enabled. However, if I install on a machine with all regional and language options set to Thai -- both "Regional Options" | "Standards and Formats" to Thai, "Supplemental language support" to include complex script support and the Advanced|"Language for non-Unicode programs" (i.e. system locale) to Thai -- then OOo automatically enabled CTL support, although it doesn't set the default CTL language to Thai. On Windows there are two independent locales: - the user locale (in XP, set on the "Regional Options" tab of "Regional and Language Settings"); this is per-user - the system locale (in XP, set in the "Language for non-Unicode programs" box on the "Advanced" tab of "Regional and Language Settings"); this is system wide not per-user The other relevant bit of data on the system is which of the 17 language groups have been installed. There's an API to check this (IsValidLanguageGroup). This is controlled by the "Supplemental language support" box on the "Languages" tab of "Regional and Language Settings". XP combines the language groups into 3 language collections: basic, east asian, and complex script. OOo currently appears to use the user locale to determine whether to enable the CTL support. Unfortunately this doesn't work very well, because it's very common for machines in Thailand for the user locale to be US (at least from my not very representative survey). Thai users are often quite happy running with a US user locale: it doesn't bother them enough that they want to change it. However, all users who want to type Thai will have the Thai language group installed. They will also almost always have Thai as their system locale: the main reason for this is that there's an undocumented Windows feature that making Thai the system locale enables the use of grave accent to switch input languages; this was the default behaviour of Thai Windows 95/98/Me, and is generally much preferred to Alt/Ctrl+Shift. I would suggest enabling CTL support if any complex script language groups are installed. For the default CTL languages, I would suggest trying first the user locale and then the system locale and using whichever is a complex script language. I'm going to try to split this up into individual issues: it's a bit too vague to be implemented as is. I'm going to try to split this up into individual issues: it's a bit too vague to be implemented as is. set target to 2.0.1 *** Issue 48123 has been marked as a duplicate of this issue. *** FT: A specification draft has been attached. This draft also covers 48123 which I have closed as duplicate to this one therefore. Note: I will publish the specification on OO.org as soon as I have access back to CVS. Created attachment 29698 [details]
Spec draft
Created attachment 29748 [details]
Spec update!
FT: Specification is now checked into CVS and available through _see URL in URL-field of this issue_. Please disregard the attached early draft from now on. Thanks. Fixed in cws thaiissues in desktop/source/app/langselect.cxx svtools/inc/languageoptions.hxx svtools/source/config/cjkoptions.cxx svtools/source/config/ctloptions.cxx svtools/source/config/languageoptions.cxx Reassigned for verification re-open issue and reassign to sba@openoffice.org reassign to sba@openoffice.org reset resolution to FIXED QA considers (parts of) this issue duplicate. Automatically setting the default document locale depending on the desktop locale is already subject of issue 32939/cws 'lo8' and integrated in m136. Hence QA insists on a resync to m136 to anticipate eventual probs. SBA->HDE: Please take over. re-open issue and reassign to hde@openoffice.org reassign to hde@openoffice.org reassign to hde@openoffice.org set back to 'resolved/fixed' . . HDE->OS: if system locale is set to 'Thai' the CTL language in office is set to 'none' and not to 'Thai' as expected The language setting is done but it's not active at the first start. Closing the office and restarting it make the setting active. Start the office on either Linux or Windows (Solaris not tested) with a CTL locale set. When the wizard starts the Linguistic.xcu contains the related CTL language as DefaultLocale_CTL property. The language setting in tools/options/language settings/languages shows no selection for CTL. sb->os: "The language setting is done but it's not active at the first start." is fixed now (desktop/source/app/langselect.cxx 1.16.40.4). Reassigned for verification . HDE: OK in CWS HDE: OK in SRC680m141 |