Bug 140894 - "Default Language for Documents" settings not operating
Summary: "Default Language for Documents" settings not operating
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.4.6.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-08 18:26 UTC by LoCall
Modified: 2022-10-06 04:12 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description LoCall 2021-03-08 18:26:15 UTC
Description:
LO
Calc

1. Have a table with French Words 
2. Click Menu Tools - Language - For All Text - More (because def is UK) - set Default Languages for Documents : Western = French - OK

French become applied in current contiguous cells in column - but not in all Text

Shift F7 to uncheck auto-spelling
Shift F7 to restart auto-spelling result red wrinkly lines still there.

F7 to try "Spelling" the non automatic way
It does show up with English UK settings

set French 
the current word loose the wrinkly red line
next word is selected 
"English UK" come up automatically in language setting

do all the "corrections"
click ok

Red wrinkly line come back overall

...
I suppose there is no need to explain what is the expected result 
...

Data 

Options/Language Settings/Languages/
Language of : UI = UK
Language of : LS = UK
Default Languages for Documents : Western = French
Default Languages for Documents : Asian CB = not checked
Default Languages for Documents : CTL CB = not checked
Enhanced Language Support (Ignore sys Input Lang) CB = not checked

Version: 6.4.6.2
Build ID: 1:6.4.6-0ubuntu0.20.04.1
CPU threads: 2; OS: Linux 5.4; UI render: default; VCL: gtk3; 
Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB
Calc: threaded


Steps to Reproduce:
1. see description
2.
3.

Actual Results:
LO not usable

Expected Results:
really ?


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
happen in several users account 
happen in 3 different computers ... one no OpenGL
Comment 1 Timur 2021-03-11 12:07:52 UTC
can you please check if can be considered duplicate of bug 136769?
Comment 2 LoCall 2021-03-11 18:36:29 UTC
Thank you Timur for have had a moment to cherry pick up this bug report.
:-)

1. - I think it is not a duplicate - explaining below why.

2. - I am ready to give you any additional info i can have / found.
     But I need some guidance.

What I have done before reporting this as a bug :
- I have done 4 researches with different keywords, 
- then I have read --all-- related with spell check and secondary language
- this have reduced the list to 21, 
- and I have carefully read theses 21 other reports.
But of course I can not exclude some have escaped to my sleuth.

I did not myself dig into the code. 
I am not familiar with LO code.

Many years of teaching (mainly C / Assembler and ArchitSys) left me the
bad habit (try to not laugh too bad at me ) to see error / bugs everywhere. 
Your updated/trained skills are here greatly needed !

But, no, I do think it is not a the same bug.

One good thing left is a good intuition to pick up the right track to spot
the bug.
In this case this bug sound more as a logic error, some function handled 
called or returned from at the right place ...

But one more time, I do not know the logic schema of LO code, you do.
I just say I have seen many time this happening the same way in other
codes...

Need more info ?
----------------

Ok, which one ?

I have already tested this on 4 computers
3 Linux + 1 Win 10 Enterprise

in all machines user profiles have been wiped out before

The same LO have been installed (up or downgraded)

2 machines have user fresh install

all machines had test done with several dictionary (second language) in FR / IT and PT_br)

all presented the very same error.

plz let me which further information could provide some help to you here ?

Kind regards
LC
Comment 3 Buovjaga 2022-03-07 08:26:37 UTC
I can't reproduce this with such a document with a table. Please test with 7.3.

Arch Linux 64-bit
Version: 7.3.1.3 / LibreOffice Community
Build ID: 30(Build:3)
CPU threads: 8; OS: Linux 5.16; UI render: default; VCL: kf5 (cairo+xcb)
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
7.3.1-1
Calc: threaded

Set to NEEDINFO.
Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away.
Comment 4 QA Administrators 2022-09-04 03:50:43 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2022-10-06 04:12:30 UTC
Dear LoCall,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp