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

RGB <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |NEEDINFO
                 CC|                            |[email protected]
           Keywords|                            |needsUXEval

--- Comment #6 from RGB <[email protected]> ---
(In reply to Eyal Rozenberg from comment #4)
> I'll then say that maybe it makes sense for
> the choice of locale to be outside the app, tied to the choice of keyboard
> layout. Because there's no reason the user should not be able to enter text
> in multiple locales in the same language group, regardless of font; and that
> action is not specific to LO, but does seem to tie nicely with the
> desktop-environment-level choice of keyboard layout. 

I disagree with that point. I use the Spanish keyboard layout to write not only
on Spanish, but also Italian and English without problems. Thanks to its dead
keys layout + AltGr combinations the Spanish keyboard can be perfectly and
easily used to write also in French, German and most languages that rely on the
Latin script*, so I don't need to learn new keyboard layouts to use different
languages, just use the correct diacritics combination. In my case and for many
people keyboard language does not correlate with the language being written. 

Also, there is an indirect, but important, relation between language settings
and fonts: languages using non Latin scripts. There are really few pan-unicode
fonts out there so if you change language to a non Latin script most of the
time you must change fonts also. 

That said, yes, the current situation is not optimal, but I'm not that sure how
to fix it.

---

* The Linux version of the Spanish keyboard layout allows to write characters
such as ß, ø, ł, â, å, etc.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to