Bug 142043 - Correct spelling wrongly flagged
Summary: Correct spelling wrongly flagged
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.1.2.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Spell-Checking
  Show dependency tree / graph
 
Reported: 2021-05-03 02:17 UTC by Stephen
Modified: 2021-12-22 08:04 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
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 Stephen 2021-05-03 02:17:17 UTC 
Description:
The spell check incorrectly flags 'disconcerting' as being incorrect. 

Steps to Reproduce:
1. write 'disconcerting'
2. flagged as incorrect
3. should not be flagged 

Actual Results:
The word 'disconcerting' is flagged

Expected Results:
Not flagged


Reproducible: Always


User Profile Reset: No



Additional Info:
[Information automatically included from LibreOffice]
Locale: en-GB
Module: TextDocument
[Information guessed from browser]
OS: Windows (All)
OS is 64bit: no
Comment 1 [REDACTED] 2021-05-03 17:28:38 UTC 
repro 

Version: 7.1.3.2 / LibreOffice Community
Build ID: 47f78053abe362b9384784d31a6e56f8511eb1c1
CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: kf5
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

when using text language "English (UK)", while the word is not flagged incorrect, when using text language "English (US)". According to:
https://dictionary.cambridge.org/dictionary/english/disconcerting

the word "disconcerting" is spelled correct in UK English.
Comment 2 Justin L 2021-09-24 13:45:05 UTC 
I cannot reproduce in 7.1.6 on Ubuntu 20.04. My normal dictionary is English (UK), and it doesn't flag "disconcerting" as misspelled. Please update and test again. If still a problem, provide a sample document.
Comment 3 Stephen 2021-12-17 02:06:22 UTC 
This bug is no longer showing. Thanks for your reply and I'd like to close this ticket