Bug 99409 - Spell Checking doesn't immediately reflect change language change
Summary: Spell Checking doesn't immediately reflect change language change
Status: RESOLVED DUPLICATE of bug 75838
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Linguistic (show other bugs)
Version:
(earliest affected)
5.0.5.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-20 09:05 UTC by Ladislav Nesnera
Modified: 2016-05-03 13:28 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
Wrong autospell highlighting (8.93 KB, application/vnd.oasis.opendocument.spreadsheet)
2016-04-20 09:05 UTC, Ladislav Nesnera 		Details
screenshot for step 2 (72.53 KB, image/png)
2016-04-26 23:16 UTC, Ladislav Nesnera 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ladislav Nesnera 2016-04-20 09:05:13 UTC 
Created attachment 124520 [details]
Wrong autospell highlighting

How to reproduce:
1. open attached file. You can see english text as red underlined by Automatic Spell Checking
2. change the language from Czech to English. Text is still underlined!
3. modify content of the cell (e.g. append " ")
4. highlighting disappear

Expected state:
Highlighting disappear immediately if language is changed.
Comment 1 tommy27 2016-04-21 01:08:21 UTC 
tested under Win8.1 x64
I see no red spell checking underline in the .ods you uploaded.

please send a screenshot and give more details about your Linux distro.

please alse tell exact steps you do to change the language
Comment 2 Ladislav Nesnera 2016-04-26 23:16:09 UTC 
Created attachment 124662 [details]
screenshot for step 2

Just right click at cell A1 and select "Format cells"

OS: Linux 4.2.6-300.fc23.i686 #1 SMP Tue Nov 10 20:12:16 UTC 2015 i686 i686 i386 GNU/Linux

LibreOffice 5.0.6.1 00(Build:1)
Comment 3 Buovjaga 2016-05-03 13:28:30 UTC 

*** This bug has been marked as a duplicate of bug 75838 ***