Re: [Vectorlinux-devel] X Configuration

[hanumizzle <han...@gm...>]

On 6/30/06, Vanger <fa...@gm...> wrote:
> In any configuration, there should be "us" layout by default. Doesn't
> matter, how much you love our native non-latin language, but you can't
> configure system by it.

OK.

>
> >         Option "XkbRules" "xorg"
> >         Option "XkbModel" "pc104"
> >         Option "XkbLayout" "us,ru(winkeys)"
> >         Option "XkbOptions" "grp:alt_shift_toggle,grp_led:scroll"
> This is the perfectly working configuration. But I always have to set
> it manually.

This is what I meant by the phrase 'just works'. c.f.
http://c2.com/cgi/wiki?ItJustWorks

> xorgconfig is dumb, when you try to set up your language in it, it
> makes a non-working configuration:
> Option "XkbLayout" "ru"
> Option "XkbVariant" "ru(winkeys)
> And if you change the default - "XkbLayout" - on "us", you can't
> switch on Russian or back.
>
> I even have seen such variant:
> Option "XkbLayout" ""us","ru""
> in a Deepstyle Linux (Russified and Ukrainized Slackware). That
> doesn't work either.

sux0rz...

>
> So, the final variant shold be:
> Option "XkbLayout" "us,<other languages>"
> Option "XkbOptions" "grp:<toggle>,grp_led:<if someone wish>"
>
>
> > * How should I integrate console keyboard support with X keyboard
> > support? Or should I let them be separate?
> It's quite easy - you have to load the needed font, load the needed
> keyboard layout and enable mapping on ttys. For Russian it looks like
> this:
>
> setfont koi8r_8x16
> loadkeys ru-ms

I'm good up to here: set the console font and load a certain
keymapping for raw keycodes.

> for n in 1 2 3 4 5 6;  // similar for all languages
> do
>         echo -ne "\033(K" > /dev/tty$n
> done

WTF? (BTW, the `seq' program can generate number sequences; it has all
kinds of features for padding and the like.)

for n in $(seq 1 6); do
  echo -ne "\033(K" > /dev/tty$n
done

Doesn't setterm -reset do something like that?

> I think, it can be automated, but I don't like the idea of integrating with X.

Here's the plan. I'll write a class for XOrgConfig that chops up an
xorg.conf. Methods for such an instance will do distinct things like:
$xorgConfig->SetDefaultDepth(16); or $xorgConfig->SetKbds(qw/en ru/);
that way individual applets can be written for each part of the
configuration...there is a lot of flexibility here. Say vkeyset does
one routine for console keyboards and another for X keyboard setup.
The other X tools will act independently of this feature. Complete
orthogonality. And the 'main' X config program will simply run
vxresset, vxmouse, vkeyset (passed -noconsole option to skip console
part).

If it doesn't make sense, I was really tired when I wrote this.

> > * cdialog configuration of X is sufficient, yes? I don't think having
> > a GUI version is really necessary.
> It is not critical, but it would be good to see it.

If I have time. I'm not sure where the practical benefit would be.

> > I don't agree. One may want to setup X keyboard via GUI.
> > KDE Control Center allows some X settings via GUI.
> But they don't work, because they rely on KDE's switcher ;) .

Does it sux0rz?

P.S. - It's good to have Russian folks working on your computer
project; their skills are undervalued IMO

--
Remember that time Thotsakan punched Neil Bush in the dick?