| Summary: | Auto Complete does weird stuff when comes to Umlauts in German (MacOS) | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | c.voelker |
| Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | NEW --- | ||
| Severity: | normal | CC: | shantanu.oak, stephan, Suchergebnisse, thomas.lendo |
| Priority: | medium | Keywords: | bibisectRequest |
| Version: | 6.4.4.2 release | ||
| Hardware: | All | ||
| OS: | macOS (All) | ||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
| Bug Depends on: | |||
| Bug Blocks: | 42082, 103341 | ||
|
Description
c.voelker
2020-06-26 08:01:39 UTC
Cannot reproduce the issue with Version: 7.1.0.0.alpha0+ CPU threads: 2; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: de-AT (de_AT.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2020-08-05_04:03:50 Calc: CL I can use word completion with Umlaut words like Gründungsjahr and ermächtigen. Also the Autocorrect options works correct and I can delete a word in the list of collected words. Maybe a Mac issue? Or one of the issues that cannot be reproduced due to user profile problems. I also observed the same problem in French on a Mac OS Catalina and LibreOffice 6.4.6 and 7. When typing an accentuated character such as é, the word was automatically autocompleted without leaving the choice (and the accentuated character is missing from the word). This means you can't type any word with accentuated characters, making Writer completely unusable. Going back to LO 6.3.6 fixed the problem. So given that c.voelker saw in on 6.4.4.2, the regression must have been introduced in 6.4.0, 6.4.1, 6.4.2 or 6.4.4. c.voelker: Has the bug reappeared after some time or did emptying the words list fix it forever? Now it gets really weird. My (not neccessarily complete) Update history is as follows. I am updating about every two month. I had installed 6.4.0 in February 6.4.3 in April 6.4.4 in June 7.0.0 since August As such I used 6.4.3 for two month and I did not notice the behaviour. I dont type much (I actually do, but mostly Emails, not formatted documents), but I should have noticed within this timeframe, so it feels save to say, that the issue started in 6.4.4. I just checked and found my word list to be empty. I dont know why. The option "clear word list when closing a document" was not checked, so there should have been at least some words, unless they did not get cleaned out during major Update from 6.x to 7.x. I opened a new text document and entered the words mentioned in the first report, among them Gründungsjahr, ermächtigen, Beschlußfassung and Beschäftigte. The collected words list now contains Gründungsjahr, ermächtigen and Beschäftigte in several forms such as Oops -sent inadvertently- I continue where I left. The collected words list contains only three of four sample words, but these words in several forms obviously generated automatically, such as ermächtige, ermächtigen and ermächtigt, but also forms that dont make sense as Beschäftig without any useful ending. The word Beschlußfassung did not get saved in the list. I kept the new document open and typed the same words again. Typing "erm" gives me the chance to accept "ermächtigt" and the word gets inserted including the Umlaut if I do. If I go on typing the Umlaut as a fourth letter myself "ermä", ignoring the suggestion, I get it replaced immediately with "ermchtigte" without Umlaut and without a chance to reject the suggestion. With Gründungsjahr it is different as I dont get a suggestion when typing only two letters "Gr", but as soon as I type "Grü", it get immediate replacement with "Grndungsjahr", loosing my "ü" and without a chance to reject the replacement. Beschäftigte same situation described for ermächtigen. There was another question on ask site (German section) about this issue: https://ask.libreoffice.org/de/question/266237/unerwunschte-auto-korrektur-in-writer/ System of the questioner: LO-Version: 7.0.1.2, OS: MacOS Catalina, Version 10.15.6 *** Bug 139308 has been marked as a duplicate of this bug. *** *** Bug 143552 has been marked as a duplicate of this bug. *** |