Bug 100194 - Problem with detection of spelling dictionaries named by BCP 47 tag
Summary: Problem with detection of spelling dictionaries named by BCP 47 tag
Status: RESOLVED DUPLICATE of bug 83376
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Linguistic (show other bugs)
(earliest affected) release
Hardware: x86-64 (AMD64) Linux (All)
: medium minor
Assignee: Not Assigned
Depends on:
Reported: 2016-06-02 17:08 UTC by Harri Pitkänen
Modified: 2016-06-20 13:37 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Harri Pitkänen 2016-06-02 17:08:48 UTC
Using spelling dictionaries for languages that have no basic locale data in LibreOffice does not work until the user accesses settings for writing aids.

Steps to reproduce:
- Create (an empty) spelling dictionary for language crl (East Cree):
  # touch /usr/share/hunspell/crl.aff
  # touch /usr/share/hunspell/crl.dic
- Start LibreOffice Writer
- Type in some text, select it and choose Format -> Character
- In the language combobox type the language code "crl" and click OK.
** Observe that there is no red underline under the text even though the
** language has changed to crl and none of the typed words exist in the
** empty spelling dictionary.
- Go to Tools -> Options -> Language Settings -> Writing Aids
- Do not change any settings, just click OK.
** Now the spell checker works and underlines all the typed words.

Expected result: spell checking should work immediately after changing the text language.

The same results can be reproduced using Voikko spell checking extension with real working dictionary so the issue is likely not related to Hunspell or using empty dictionary.
Comment 1 Buovjaga 2016-06-08 15:27:42 UTC

Arch Linux 64-bit, KDE Plasma 5
Build ID: c6d553b5fac93d97cb0d316586db34f4d5a8def1
CPU Threads: 8; OS Version: Linux 4.5; UI Render: default; 
Locale: fi-FI (fi_FI.UTF-8)
Built on June 3rd 2016
Comment 2 Urmas 2016-06-20 13:37:10 UTC

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