Anyone working on XKB support for Wine (or any other Keyboard language detection enhancements)?

[Shachar Shemesh]

Hi all,

The current keyboard detection and setting code is based on the
traditional method of setting a keyboard in X11. It misdetects most any
language that carries a US keyboard as the first group. While major work
on other areas of Wine means that most programs today don't really care
about that, it still confuses the $*(!@#&$ out of Word. It also has some
pretty serious BiDi editing implications.

I'm looking into replacing that with code based on the XKB X11
extension, today supported with any quasi reasonable X server. This
should totally eliminate the guesswork done through keyboard change
detection in wine today.

The main question is this - is anyone today already working on this?

Thanks,
Shachar

[Oleh R. Nykyforchyn]

Shachar Shemesh <shachar(a)shemesh.biz> wrote:
> The main question is this - is anyone today already working on this?

I do it for three years with almost zero responce from Wine team. See, e.g., my post to wine-devel, Mon, 13 Nov 2006.
If You care, I can upgrade my patch against current Wine release and send it to You.

Oleh

Anyone working on XKB support for Wine (or any other Keyboard language detection enhancements)?

[Jan Zerebecki]

On Mon, Apr 02, 2007 at 04:37:54AM +0300, Oleh R. Nykyforchyn wrote:
> Shachar Shemesh <shachar(a)shemesh.biz> wrote:
> > The main question is this - is anyone today already working on this?
> > I do it for three years with almost zero responce from Wine team. See, e.g., my post to wine-devel, Mon, 13 Nov 2006.
> > If You care, I can upgrade my patch against current Wine release and send it to You.

This usually is a good sign. I know, it's not encouraging to get no
feedback, but sadly this is how it works here. If your patches didn't
get applied after sending to -patches and you didn't get feedback yet,
the best way is usually to ask AJ on IRC. For a patch of this extend it
is also a good idea to talk with AJ beforehand so there is an agreement
how to proceed.

Would this also fix the following bug or does that have nothing to
do with the work at hand?:
Bug 1181 - Keyboard translation broken: uses raw keycodes?
http://bugs.winehq.org/show_bug.cgi?id=1181


Jan