https://bugs.documentfoundation.org/show_bug.cgi?id=154795
--- Comment #9 from Eyal Rozenberg <eyalr...@gmx.com> ---
(In reply to RGB from comment #6)
Let me first point out that this thread of discussion we're having is
independent of this bug...
> (In reply to Eyal Rozenberg from comment #4)
> 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.
I'm not suggesting you be forced to use a keyboard layout you don't like. The
question is of the mechanism you use to express the fact that "I'm writing
Italian now", "I'm writing Spanish now" etc. Sometimes, you don't care about
expressing this fact; but you do need to express it to use features like
spelling check / dictionary, hyphenation etc. what I'm saying is that:
* It makes sense for this mechanism not to be application-specific - just like
setting the keyboard layout is not an application-specific thing.
* It would be convenient to piggy-back onto the keyboard layout setting
mechanism(s). That does not mean keyboard layout chosen = language used; but
the same dialogs, utilities, task bar / panel icon etc we use for setting the
keyboard layout should also be used to set the input's locale / language +
country. So you should be able to say "I'm now going to enter text in the
English language, localized for Australia, and using a Spanish keyboard
layout".
> 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's why we don't set fonts, we set font-sets. Quoting from the example in
bug 151215, Comment 19:
<a:minorFont>
<a:latin typeface="Calibri" panose="020F0502020204030204"/>
<a:ea typeface=""/>
<a:cs typeface=""/>
<a:font script="Jpan" typeface="游明朝"/>
<a:font script="Hang" typeface="맑은 고딕"/>
<a:font script="Hans" typeface="等线"/>
<a:font script="Hant" typeface="新細明體"/>
<a:font script="Arab" typeface="Arial"/>
<a:font script="Hebr" typeface="Arial"/>
<a:font script="Thai" typeface="Cordia New"/>
etc. etc.
this is how it's done in MSO. Unfortunately, LO's font-sets only have 3 fonts
in a font-set: western, RTL-CTL and CJK. But this deficiency is acknowledged
and - at some point - will be rectified.
--
You are receiving this mail because:
You are the assignee for the bug.
