Pablo Saratxaga wrote:
> > I know that all non-latin layouts are really two-layout maps where the first
> > layout is 'US qwerty'. And we have to keep all of them at least some time.
> > For new maps I'd suggest to use a special name extension (for example,
> > .sg - 'single group') or place them in new subdirectory (for example,
> > symbols/layouts).
>
> But that means duplicating half of the files; it's a real waste.
I meant those files will coexist only while time for migration from
a present layout model to new one.
In MS Windows when I choose 'Russian keyboard' I get the russian keyboard
map only without any latin ones. And non-latin writing Windows user know
they need to choose 'en' keyboard explicitly (as primary or secondary one)
if they want it.
The same can be done with 'XKB multi_layout model'. All non-latin writing
users should specify 'us,ru' (or 'en,ru') layouts when they need it.
But if you suppose it too difficult for Unix users ... OK.
For case where only one (non-latin) layout name is specified we can write
rules like
! model layout = symbols
... ru = base+us.sg+ru.sg:2
and avoid duplication.
> Better would be to have a special keyword or something so the files
> can remain single group, but be identified as non-latin; and if such
> a file is loaded alone, then silently add "us" layout in group 1 and switch
> the asked file to group 2.
I can't imagine where this 'special keyword' can be placed and checked
but at least we can mention all such layouts in rules
... ar = base+us.sg+%l.sg:2
... il = base+us.sg+%l.sg:2
... ru = base+us.sg+%l.sg:2
etc.
I suppose it is not too bad.
> > I don't know how to assign (in the XKB) a key description to keysym
> > instead of keycode name. (The xmodmap has such posibility but it seems to me
> > rather dangerous.)
>
> It should be allowed only for group 2 and up, not for the first one.
> So there will always be a clean layout.
Indeed.
> > But the XKB has so called 'keycode aliases' that can help, I suppose.
> > We can compose special xkb_keycodes files with such aliases ( with
> > "alias <LATA> = <AC01>" for 'us' keyboard and "alias <LATA> = <AD01>
>
> It would be better to implement a new and specific support for real
> keysyms aliases (if the idea seems ok, if not, it is not that important).
It could be better but need deep changes for xkb files parser.
Therefore let stay on my solution with keycode aliases.
--
Ivan U. Pascal | e-mail: [EMAIL PROTECTED]
Administrator of | Tomsk State University
University Network | Tomsk, Russia
_______________________________________________
I18n mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/i18n
