Issue 124551 - word completion suggestion all capitalized, word in database is mixed case
Summary: word completion suggestion all capitalized, word in database is mixed case
Status: CONFIRMED
Alias: None
Product: Writer
Classification: Application
Component: editing (show other issues)
Version: 4.0.1
Hardware: All All
: P3 Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2014-03-29 16:51 UTC by aeneumann
Modified: 2014-05-08 20:22 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description aeneumann 2014-03-29 16:51:34 UTC 
Word completion adds BWL-Vorlesung to its list, then suggests BWL-VORLESUNG at the next occurence. ctrl+tab does nothing as there is only one possible word completion (which has been replaced with wrong capitalization in the suggestion). The word completion list contains BWL-Vorlesung before and after trying to use word completion and does not contain BWL-VORLESUNG. The wrong capitalization is suggested until you have written the first lower case letter, i.e. BWL-Vo, then it correctly suggests BWL-Vorlesung.

This is a new bug in Writer 4.0.1 that did not exist in 3.x.x (the version I upgraded from. I think it was 3.4.x). It is very annoying as I write technical texts and words like BWL-Vorlesung appear a lot in them. BWL-Vorlesung is a correct and correctly capitalized German word (term?).
Comment 1 mroe 2014-03-29 17:58:32 UTC 
I can confirm this issue as described with 4.0.1.

But with 4.1 beta nothing happens. Can anyone other please check, if there is a new bug that nothing is collected?
Comment 2 aeneumann 2014-05-08 20:16:23 UTC 
The 4.1.0 release version has this bug again. Wondering how it got dropped out and back in during the beta.
Comment 3 aeneumann 2014-05-08 20:22:29 UTC 
(In reply to aeneumann from comment #2)
> The 4.1.0 release version has this bug again. Wondering how it got dropped
> out and back in during the beta.

scratch that. misread mroe's comment. Thought it said bug was fixed in 4.0.1. So yeah, this bug is still not fixed and no fix has been attempted it seems.