Description: What is the purpose to have **Enable word completion** and **Collect words** settings separated? (Tools > AutoCorrect > AutoCorrect Options > Word Completion.) Both settings * are global * are stored only in the application and never in the document, and so once you disable one of them, the other will stop making any practical effect. And so I don't see any reason to have them separated. **Test 1:** You have "Enable word completion" disabled and "Collect word" enabled. Then you start LibreOffice. Word completion wouldn't work, of course. **Test 2:** You have "Collect words" disabled and "Enable word completion" enabled. Then you start LibreOffice. Word completion wouldn't work either, because there are simply no words for it. The only situation in which changing one of these settings will make a different practical effect than changing both of them is when you already have some document opened. But I don't think this is how it is assumed to be used. Steps to Reproduce: - Actual Results: - Expected Results: - Reproducible: Always User Profile Reset: No Additional Info: -
How about adding words from a special dictionary? Not implemented however. And it makes absolutely no sense to collect words but having the word completion disabled.
(In reply to larson from comment #0) > Description: > What is the purpose to have **Enable word completion** and **Collect words** > settings separated? (Tools > AutoCorrect > AutoCorrect Options > Word > Completion.) It allows users to use collected words - e.g. in a file containing complicated special terminology - without collecting new.
Created attachment 183462 [details] image comparing LO 330 - 74x UI for the autocompletion options
The topic was on the agenda of the design meeting but didn't receive further input. To summarize: One should be able to use autocorrection without collecting new words, so we need a checkbox at the right side. And users want to disable the autocorrection completely, so we also need an option at left. It's questionable whether left off / right on makes sense but there might be rare use cases. => NAB