https://bugs.documentfoundation.org/show_bug.cgi?id=168624

--- Comment #5 from Eyal Rozenberg <[email protected]> ---
First, a question What are "proofing languages"? I don't see those anywhere in
Tools > Options. Do we have a feature involving those?

Now, while I agree that choosing "one default language", and per artificial
languiage group, is kind of silly - it is an actual setting that LO has and
uses - for the language choice in the default paragraph style of documents (at
least, LO is supposed to be doing that). While the trichotomy is in place, I
disagree with crippling users' ability to configure the app as it is. So, I
oppose this implicit setting via an opaque prioritization of languages; users
will just have to do a different kind of guessing.

I doubly object because this will place an even more powerful mask on full
support toggles for the RTL-CTL and CJK language groups. Yes, it's true that
users might get support enabled "for free" - but they might miss that, not
caring about "proofing languages", and not find the setting anywhere. No, this
is not good enough. On the contrary: What I would like to see is:

1. More panes in the navigation tree which, when clicked, suggest enabling full
support for the relevant language group (or just allow enabling it right
there).
2. A separate section for just the two toggles of support for RTL-CTL and for
CJK, with an attractive title, e.g. "Full support for languages", separately
from default language choice, and
3. A clearly-worded label for each of these checkboxes, e.g.: "Enable full UI
support for Right-to-Left and Complex-Text-Layout text" and "Enable full UI
support for CJK East-Asian languages". This can be bikeshed of course. 
4. Perhaps a warning message at the bottom of this pane, that dismissing this
dialog may hinder use of LibreOffice with written language such as X, Y and Z
from the two groups. Kind of like a "Ministry of Health Warning" sticker.

... and maybe something to direct the user to the right place in the nvaigation
pane.?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Reply via email to