Micha Feigin wrote:
Sorry, sent off list by mistake
On Mon, 9 Mar 2009 22:05:51 +0100
Jean-Marc Lasgouttes <lasgout...@lyx.org> wrote:
There are two issues. For running the dictionary you need to know
For hebrew and arabic it's another issue, you need to know the
so that you know directionality. Hebrew is right to left. For
it may be easy to decide, for what about spaces and numbers? For
these we need
to know the system keyboard language and not guess it from the
So you want to change language when the keyboard layout is changed at
system level, right?
I never thought of these layouts as indicators of the actual
language. If Qt gives us
Under windows I know it's possible since for example word does it.
whether this is possible to know under linux (I guess so since
there are panel
applets that show the language). Which again comes down to the
there is a technical issue why to work this way or not.
this information, we should be able to do it.
For every other program the system language is used for input (alt-shift in my
case). So for example when writing mail or using oowriter I change the system
language to change input. Lyx is the only exeption where I __have__ to keep the
system language for english and bind (f12 in this case) to language hebrew. It
makes things incosistent and non-intuitive, esspecially for new users.
I agree. For RTL languages, it makes a lot of sense to change the
current language together with the system. Advanced users wishing to
change the language independently should be able to disable this feature
Now, you have to find someone willing to implement this feature ;-)
FYI, a year or two ago I advocated that the text direction should be
based uniquely on the encoding, independently of the language settings,
like Qt does. But I failed to convince other developers.
Dov, are you reading this? ;-)