Bug 122277 - tools / language / for all text -- allow us to define (most frequently) used languages
Summary: tools / language / for all text -- allow us to define (most frequently) used...
Status: RESOLVED DUPLICATE of bug 85449
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected)
Hardware: All All
: medium enhancement
Assignee: Not Assigned
Depends on:
Reported: 2018-12-22 09:15 UTC by peter josvai
Modified: 2018-12-31 09:45 UTC (History)
2 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 peter josvai 2018-12-22 09:15:18 UTC
that there are so many languages in LiO, is a very good thing...
it is beautiful that all people on this Planet, in this civilization, can use a writing tool like Writer.. without limitations whatsoever...

AT the same time, 
I barely use more than 2 languages, and I have to make the way from 
"tools / language / for all text"  (or for selection) ...

and often... I'll have to go on to "more options" 
to set my second most frequently used language as the language of the document..

AND not only that..
when I'm doing that, I'll have to scroll through that list...

- - - -

my suggestion:
the long list is COOL.. even beautiful...
it would be great, however, if one could make some sticky decisions...

like, keep this one in the "short list" (tools / language /for all text / ...)

that is, it would be great to have a "most frequently used" category...
that could be saved...

I imagine that those who write and edit text in 3-4 languages, would be extremely grateful :)

it would be great if some languages would not automatically show up as selectable in  "tools / language / for all text ..." menu...

like for me right now: {tzm-latn} :) 
just because I badly misspelled a word at the beginning of a new text :)

thank you for developing Libreoffice !!
happy holidays!
Comment 1 Heiko Tietze 2018-12-31 09:45:44 UTC
While bug 85449 is talking about a solution and not an issue (filtering is one option, here a flag is proposed, and I can figure many other ways to deal with very long lists) it's still the same problem.

*** This bug has been marked as a duplicate of bug 85449 ***