Re: ukrainian layout

[Dmitry Timoshkov]

"Andy Rysin"  wrote:
> Also I had to modify unicode/cp20866.c (KOI8-R) to allow conversion
> of additional 4 pair of letters in Ukrainian language (KOI8-U,
> RFC2319) as well as one additional pair of letters for Belorussian
> language (AKA KOI8-RU, which does not have RFC though). 
> Strictly speaking KOI8-R is a subset (if not to take to account
> pseudographics) of KOI8-U wich is a subset of KOI8-RU.
> That's why I applied it to cp20866.c instead of creating smth new.
> (I took it from my patches for linux kernel nls system)

You can't modify cp*.c files, they are auto generated from the unicode.org
file set. You need to send your patch to the unicode.org maintainers and
hopefully it will be included in the next Unicode Standard release.
> Another problem is that I could not test it practiacally because for
> some reason Win32 programs under wine does not input cyrillic
> letters, but if I swicth to X program and then back it stops input at
> all if layout is cyrillic. If I swicth back to latin everything's ok.

It's a known problem, that Wine's x11 keyboard driver does not work with
"non-sticky" switches. I have tested cyrillic input with XFree86 3.3.6,
4.0.3 and 4.1.0 with KDE and KiKbd, all works fine for me.

Proper support for non-sticky modifiers, dead-keys and the real keyboard
layout support requires almost complete keyboard driver rewrite.
> BTW, why not to take layouts from X system itself?
> Those wich are under /etc/X11/xkb/symbols

Because XFree86 is not the only X11 implementation out there.

--
Dmitry.

ukrainian layout

[Andy Rysin]

--- Dmitry Timoshkov  wrote:
> You can't modify cp*.c files, they are auto generated from the
> unicode.org
> file set. You need to send your patch to the unicode.org
> maintainers and
> hopefully it will be included in the next Unicode Standard release.

does that mean that there'll be no koi8-u support until it appears in
Unicode standard descriptions? can we add manual file cp20866u.c?
It was not a problem for all other projects I made koi8-u into (Linux
kernel nls, PostgreSQL).

Also would UA kerboard part of the patch go into the project
anywhay??
> It's a known problem, that Wine's x11 keyboard driver does not work
> with
> "non-sticky" switches. I have tested cyrillic input with XFree86
> 3.3.6,
> 4.0.3 and 4.1.0 with KDE and KiKbd, all works fine for me.

What does mean "non-sticky" switches? Currently I use KDE 2.2 with
kxkb and I start wine with UA layout turned on.
Thanks,
Andriy

__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger
http://im.yahoo.com

ukrainian layout

[Dmitry Timoshkov]

"Andy Rysin"  wrote:
> > You can't modify cp*.c files, they are auto generated from the
> > unicode.org
> > file set. You need to send your patch to the unicode.org
> > maintainers and
> > hopefully it will be included in the next Unicode Standard release.
>
> does that mean that there'll be no koi8-u support until it appears in
> Unicode standard descriptions? can we add manual file cp20866u.c?
> It was not a problem for all other projects I made koi8-u into (Linux
> kernel nls, PostgreSQL).

I'm afraid you can't, because code page 20866 (aka 878) already assigned.
> Also would UA kerboard part of the patch go into the project
> anywhay??

I don't see any obstacles for that.
> > It's a known problem, that Wine's x11 keyboard driver does not work
> > with
> > "non-sticky" switches. I have tested cyrillic input with XFree86
> > 3.3.6,
> > 4.0.3 and 4.1.0 with KDE and KiKbd, all works fine for me.
>
> What does mean "non-sticky" switches? Currently I use KDE 2.2 with
> kxkb and I start wine with UA layout turned on.

x11drv waits for MappingNotify event to reinitialize its internal
keyboard mapping. You might want to debug why that event doesn't get
generated in your case.

--
Dmitry.