[Libreoffice-ux-advise] [Bug 62063] FORMATTING: Font textbox ignores keyboard layout change to RTL language

[bugzilla-daemon at bugs.documentfoundation.org]

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

--- Comment #26 from Heiko Tietze <heiko.tietze at documentfoundation.org> ---
Had a long discussion with Hossein about this ticket (who thinks this is a
plain bug) and related topics. As UX input was requested we have to consider
the whole picture.

1. Of course we can change the three scripts concept and configure fonts per
language, which would be an extendable list picked from all languages. For
example English = Sans, Hebrew = AlefAlef, Arab = Madani.
Pro: It's possible to define one font for every language; the hidden controls
could be visible but also hidden depending on a predefined subset
Con: Users might be familiar with the 3-script concept from Windows;
configuring the hell out of the software is seldom desired

2. The most focal issue is that typing with a non-English character set should
be recognized and have an effect on the text. It's expected that entering ABC
makes this part English, АБГ becomes Russian, and ابت magically Arabic (ideally
with the right country taken from locale). The appropriate font should be used,
paragraph and character settings applied, and all tools including dictionaries
just work properly. MSO works like this and changes the input language
depending on the typed characters. 
Con: The language is part of the PS and the CS, as well as direct formatting.
Switching magically makes it harder to understand the concept.
Pro: Convenience and usability; and we could keep the language if defined
somehow
Remark: The task to detect the language is likely not trivial.

3. Back to 1: Providing defaults for so many styles is an overkill and makes it
unclear what the supposed workflow is (templates overwrite tools > options). We
could drop this concept and _allow_ to define _one_ font for the Default PS per
locale setting.

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