Bug 93926 - Correct word is corrected to wrong word (Differenzeierbarkit)
Summary: Correct word is corrected to wrong word (Differenzeierbarkit)
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Localization (show other bugs)
(earliest affected) release
Hardware: Other Linux (All)
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: AutoCorrect-Complete
  Show dependency treegraph
Reported: 2015-09-04 15:55 UTC by michelbach94
Modified: 2020-09-25 18:46 UTC (History)
4 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 michelbach94 2015-09-04 15:55:34 UTC
"Differenzierbarkeit" is a German word but is shown as incorrect. Instead, "Differenzeierbarkit" is proposed which has 2 spelling errors in it.
Comment 1 Julien Nabet 2015-09-04 23:09:04 UTC
Which LO version do you use?
On which env are you? (Windows, MacOs, Linux)
Comment 2 Xisco Faulí 2016-09-11 13:41:12 UTC Comment hidden (obsolete)
Comment 3 michelbach94 2016-09-11 13:45:46 UTC
Build ID: 1:5.1.4-0ubuntu1
CPU Threads: 8; OS Version: Linux 4.4; UI Render: default; 
Locale: en-US (en_US.UTF-8)
Comment 4 Julien Nabet 2016-09-11 20:19:30 UTC
On pc Debian x86-64 with master sources updated today, I don't reproduce this.

However with LO Debian package 5.2.0, I could reproduce this.
(hunspell-de-de: version 20160407-1)

Sophie/Adolfo: thought you might be interested in this one. I must recognize I don't understand why I don't reproduce this with master sources, doesn't it use same hunspell-de-de package?
Comment 5 Adolfo Jayme 2016-09-11 22:51:35 UTC
It would be good to track down whether this issue happens only with the distro-packaged hunspell or not
Comment 6 Xisco Faulí 2017-09-29 08:49:00 UTC Comment hidden (obsolete)
Comment 7 michelbach94 2017-09-29 13:40:45 UTC
Bug is still present.
Comment 8 QA Administrators 2018-09-30 02:48:04 UTC
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword

Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team