Bug 55083 - "Replacements and exceptions for language:" (AutoCorrect d.box) should follow "Default languages for documents: Western" (Options)
Summary: "Replacements and exceptions for language:" (AutoCorrect d.box) should follow...
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
3.3.3 release
Hardware: All Windows (All)
: high normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: needsUXEval
Depends on:
Blocks: AutoCorrect-Complete Options-Dialog-Language
  Show dependency treegraph
 
Reported: 2012-09-19 08:59 UTC by Kumāra
Modified: 2020-04-23 13:27 UTC (History)
6 users (show)

See Also:
Crash report or crash signature:


Attachments
Options - Languages (26.79 KB, image/gif)
2013-02-09 07:31 UTC, Kumāra
Details
AutoCorrect dialog box (21.21 KB, image/gif)
2013-02-09 07:39 UTC, Kumāra
Details
Text to Columns (Import text) (18.69 KB, image/gif)
2013-02-09 07:40 UTC, Kumāra
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kumāra 2012-09-19 08:59:48 UTC
LibO is not using the Locale setting (in Languages options) intuitively. In at least two places, it is taken as the Default Language:
1. Writer's AutoCorrect Options dialog box
2. Calc's Text Import dialog box

E.g., when I have "Malay (Malaysia)" as the Locale setting (I live in Malaysia), the currency is rightly reflected as "MYR RM Malay (Malaysia)". Fine. However, this leads to the above issues, i.e., Malay is set as the default language in those dialog boxes, although I specified the Default Language in Options as "English (UK)".

Is this on purpose or a mistake? If on purpose, I would like to question the rationale.
Comment 1 Kumāra 2013-01-23 08:44:16 UTC
Sorry if "I would like to question the rationale" sounded a bit rude. I didn't mean to be. Hope someone would look into this. Presently, I'm circumventing it by not having the right locale set.
Comment 2 Thomas Arnhold 2013-02-08 04:50:15 UTC
Hi Kumāra,

please could you give some more information about it? Screenshots with Malay and English behavior would be nice.

Thomas
Comment 3 Kumāra 2013-02-09 07:31:36 UTC
Created attachment 74471 [details]
Options - Languages
Comment 4 Kumāra 2013-02-09 07:33:21 UTC
Comment on attachment 74471 [details]
Options - Languages

Note Locale setting and Default Language (western)
Comment 5 Kumāra 2013-02-09 07:39:13 UTC
Created attachment 74473 [details]
AutoCorrect dialog box

Notice that the automatically selected language is Malay (Malaysia), not /English (UK).
Comment 6 Kumāra 2013-02-09 07:40:44 UTC
Created attachment 74474 [details]
Text to Columns (Import text)

Notice dimmed "Malay (Malaysia)".
Comment 7 Kumāra 2013-02-09 08:00:47 UTC
Comment on attachment 74473 [details]
AutoCorrect dialog box

For someone who is unaware of this bug, if he makes a change to the locale setting, he would later be wondering why everything under AutoCorrect aren't working.
Comment 8 Kumāra 2013-02-09 08:04:48 UTC
Thank, Thomas, for the attention to this. It's not a show stopper, but it can be bewildering and frustrating for one who's using English, and have set the locale setting to a non-English locale.
Comment 9 tommy27 2013-08-30 12:15:01 UTC
@Kumara
do you still see this bug with recent LibO 4.0.5 or 4.1.1 releases?
Comment 10 Kumāra 2013-08-31 04:22:05 UTC
(In reply to comment #9)
> @Kumara
> do you still see this bug with recent LibO 4.0.5 or 4.1.1 releases?

Yup. How's it like on your side? Have you tried it?
Comment 11 tommy27 2013-08-31 12:20:24 UTC
I have italian localization and italian interface on Windows7 64 bit. 
never had such issues.
Comment 12 Kumāra 2013-09-01 04:22:10 UTC
(In reply to comment #11)
> I have italian localization and italian interface on Windows7 64 bit. 
> never had such issues.

And what do you have as "Default language for documents"?
Comment 13 tommy27 2013-09-01 05:42:55 UTC
now I understand what do you mean.

I never had issues since my predefined language was italian and it matched GUI and locale settings.

I tried changing to english in the options menu (Language Settings / Language / Default language for documents / Western)....

if I select English (USA) it works until next restart where default language turns back to italian. when you reopen the option menu you will that the previous language change doesn't stick.

if I select other English variants (UK, Australia, Namibia ecc. ecc.) or another non-English language (I tried Zulu) the change stick.

can you confirm my findings? You said you had issues with English UK while I have the problem with English USA.

bug was first reported in 3.6.5.2 (please Kumara specify your O/S)
and is still present on 4.1.1.2 under Win7 64 bit. 
was already reproducible in earlier versions (tested up to 3.3.3)

Interestingly the issue is not present in 4.2.0.0.alpha0+
Build ID: 94730f359023a3e90fd6d5239a12a150f41f4dd2
TinderBox: Win-x86@39, Branch:master, Time: 2013-08-31_03:30:47

In 4.2 alpha0+ English (USA) sticks unlike previous releases.

If developer identify the cause of different behaviour between final releases and 4.2 alpha they could backport it to 4.1.x

changing status to NEW and adding Writer and Localization experts to CC list.
changed version to 3.3.3
Comment 14 tommy27 2013-09-01 05:56:44 UTC
*** Bug 40657 has been marked as a duplicate of this bug. ***
Comment 15 tommy27 2013-09-01 05:58:25 UTC
I paste below interesting informations from Bug 40657
------------------------------------------------

At2010  2011-09-06 11:17:22 UTC 
using LO 3.4.3 on Windows 7 x64

Clean (initial) install of LibreOffice.

In Language settings of Tools/Options/Language Settings/Languages.

The install correctly detects my user interface as English (USA). However, it incorrectly fills in Locale as English (Zimbabwe) and Language for Documents (Western) also as English (Zimbabwe).

I think that the language/locale default setup is using either the last index for a given language or a +1 index. In the case of English, there are about 15 locales, Australia to Zimbabwe. USA is listed as 14, Zimbabwe as 15.
If an index search for UI system setting English (USA) matches a locale in LibreOffice, it may be counting 1 as the first entry rather than 0. This could cause a 1 off index return.

After setting the locale to English (USA) and document language to the same, the options are correctly maintained.

But setting the locale does not change the measurements for margins and tabs like it does for currency. Changing to English (USA) should switch to measurements customary for the locale. In this case: Inches.
Comment 16 Kumāra 2013-09-01 07:24:52 UTC
(In reply to comment #13)

I wondered if you may have identified a different issue. So, I tried to explain to you how to replicate it. While doing so, I found that I can't replicate as before! Something must have changed in the latest version I'm using (4.1.1.2).

However, as you experienced, upon restarting LibO, the bug become apparent again. Following my original report, the "Replacements and exceptions for language:" indicates "Malay (Malaysia)".

This is consistent with the "Locale setting" (in Tools - Options - Language Settings - Languages).

By right (according to my logic), it should follow "Default languages for documents: Western" (which I indicate as "English (UK)").
Comment 17 tommy27 2013-09-01 08:38:14 UTC
(In reply to comment #16)
> (In reply to comment #13)
> 
> I wondered if you may have identified a different issue. 

maybe it's a different issue...
"Default language for documents" is the language to use when you open a blank new document. The option settings resets when I choose "English (USA)" and reverts to "locale settings" but sticks there when I choose other languages. 
This is certainly a bug.

have you tried changing from "English (UK)" to "USA" and see if the change remains after closing or reverts to your Malaysian locale?

p.s. (Language Settings / Language / Default language for documents / Western)

> So, I tried to explain to you how to replicate it. While doing so, I found 
>that I can't replicate as before! Something must have changed in the latest  >version I'm using (4.1.1.2).
> 
> However, as you experienced, upon restarting LibO, the bug become apparent
> again. Following my original report, the "Replacements and exceptions for
> language:" indicates "Malay (Malaysia)".

I confirm this in autocorrect. Despite having set Default language for documents as "English (Namibia)", when I load the autocorrect options menu it loads my locale setting list "Italian", if I change it to "English (Namibia)" it stays there until relaunch when Italian locale list lost pops out again.

> This is consistent with the "Locale setting" (in Tools - Options - Language
> Settings - Languages).
>
> By right (according to my logic), it should follow "Default languages for
> documents: Western" (which I indicate as "English (UK)").

as you may see the autocorrect replacement table follows the "Locale Settings" and not the "Default language for documents". Unlike the bug I reported before there's no change in the "Default language for documents" user selection.
I agree to your logic... autocorrect should follow "Default language for documents".
Comment 18 tommy27 2013-09-01 09:04:41 UTC
(In reply to comment #14)
> *** Bug 40657 has been marked as a duplicate of this bug. ***

after reading better that bug description I think it's not a duplicate of the current one.
Comment 19 Kumāra 2013-09-02 02:59:30 UTC
(In reply to comment #18)
> (In reply to comment #14)
> > *** Bug 40657 has been marked as a duplicate of this bug. ***
> 
> after reading better that bug description I think it's not a duplicate of
> the current one.

I agree. Better undo it over there.

As for this bug report, I wonder if it's too messy to read now. Coders probably wouldn't want to sift through it, as we can't edit/delete our comments.

So, I wonder if we should redo this. Besides, I now think I can rephrase my whole report to make it more concise and precise.

What do you think?
Comment 20 Cédric Bosdonnat 2014-01-20 09:00:36 UTC Comment hidden (noise)
Comment 21 Julien Nabet 2015-03-22 20:10:54 UTC
Kumara: could you give an update with recent LO versions (4.3.6 or 4.4.1)?
If you still reproduce this, I thought about asking advice to ux-team
Comment 22 Kumāra 2015-04-20 05:31:53 UTC
(In reply to Julien Nabet from comment #21)
> Kumara: could you give an update with recent LO versions (4.3.6 or 4.4.1)?
> If you still reproduce this, I thought about asking advice to ux-team

Sorry for the late response. I'm still on 4.1.6.2, due to a regression bug I'm not willing to tolerate. A patch has been made for 4.4.3. Will check then and let you know.
Comment 23 QA Administrators 2015-12-27 20:31:43 UTC Comment hidden (obsolete)
Comment 24 Kumāra 2015-12-31 00:31:37 UTC
(In reply to Julien Nabet from comment #21)
> Kumara: could you give an update with recent LO versions (4.3.6 or 4.4.1)?
> If you still reproduce this, I thought about asking advice to ux-team

Yes, still present, in LO 5.0.2.2.

Although the note says I should set it the status back to UNCONFIRMED, I'm setting it to NEW, because it was already confirmed earlier and nothing has changed.
Comment 25 Julien Nabet 2015-12-31 07:41:24 UTC
Thank you Kumara for the update.

ux-team: any thought about this one? Is this a bug or is this on purpose?
Comment 26 Heiko Tietze 2015-12-31 08:28:32 UTC
According all the previous comments it is a bug. And I hardly can imagine any reason to not use the default doc language for the auto correct feature.
Comment 27 Robinson Tryon (qubit) 2016-08-25 05:39:18 UTC Comment hidden (obsolete)
Comment 28 Heiko Tietze 2020-04-20 16:30:41 UTC
Tools > Options > UI: English, Locale: German, Document Language: German -> new document is in German as well as autocorrect options. Shortcuts such as dummy text (dt+F3 for English) are not changed (German would be bt+F3) and also the inserted content is not localized. It follows the UI, which makes sense to me. Don't see need to change this.
Comment 29 Heiko Tietze 2020-04-23 13:27:58 UTC
We discussed the topic in the design meeting and agreed on resolving it as WFM. Please reopen in case it's still an issue and the settings at tools > options are not sufficient.