Description: The language lists in "Tools > Language > For Selection / For Paragraph / For All Text" get cluttered up with unused languages previously chosen through the "For Selection > More..." dialogue. When the bug is not triggered by changing the language "For Selection", choosing different languages "For Paragraph" and "For All Text" works as expected. The newly chosen language will replace the language previously assigned to a paragraph or the whole document. Changing the language "For All Text" will correctly remove all other languages from the language selection lists. In addition, only the language list "For Selection" correctly indicates the used language with a check mark. This is either not implemented or not working "For Paragraph" and "For All Text". Maybe someone liked the idea of "recently used languages" and a check mark to indicate the currently used language, but it was only implemented "For Selection", causing the other language lists to behave inconsistently? Steps to Reproduce: 1. Open/create a new Writer document. 2. Write "test text", and select the word "test". 3. Change the language "For Selection" to several different languages. Actual Results: The language lists contain all recently chosen languages, up to a maximum of seven different languages. Even changing the language "For All Text" does not remove unused languages from the list(s). Expected Results: The language lists should only contain the default language and the last selected language or, in other words, languages used in the current document. Reproducible: Always User Profile Reset: Yes Additional Info: (Tested on Windows 10 and Ubuntu)
I confirm the described behaviour, but I can't assess, if it is a bug or not. So let's ask design-team. Steps to Reproduce: 1. Open/create a new Writer document. 2. Write "test text", and select the word "test". 3. Tools -> Language -> For Selection -> More 4. Select any language -> OK 5. Repeat steps 3 and 4 several times Actual and expected result: see comment 0
The language menu picks up what users have defined in the document. It's not much of a surprise to see a long list after picking many different languages, quite unlikely however as a real world scenario. And long/cluttered has room for discussion. Anyway, we decided recently on bug 95274 comment 70 what strategy might be the best. My take here: WF/NAB.
Agree -1, and => WF/NAB