Preliminary OLPC xkb definitions

[Sergey Udaltsov]

> Sounds like a broken keyboard or kernel map to me.  But, regardless, why
> not make keycodes/olpc if you really need to, and have model olpc
> include that?
Well, I am not in favor of creating multiple keycodes unless we have
to. First, I'd love to get to the bottom of the problem whether it is
a bug in evdev driver or what?

> This should probably be symbols/olpc, but Sergey can feel free to
> correct me on this one.
Well, I do not mind either way, actually. I do not know whether olpc
should be considered as a "kind of PC" or not. Never seen it.

> > +    key <AK01> { [ A1  ] };
> This sounds like a really bad set of keysym names.
Yes, keysym A1 looks rather suspicious...

> Do we not have X keysyms for all the Thai glyphs?
IIRC we don't - but it is worth double-checking anyway

> This belongs in the generic OLPC set, not in the Thai layout.
Or rather XkbOptions.

> The whole patchset looks pretty sketchy to me.  And I'm assuming it
> depends on some rules changes and also keysym additions which aren't
> published.

Yes, as I said, I am eager to see updated rules...

Sergey