Hi all
Short summary: I see a problem with combining several layouts in the way
"encouraged by XKB. An example to that problem is the question: how do I
create a layout of "English(US)+Romanian+Hungarian"
standard keyboard mappers (e.g: KDE's kxkb, window's internat) show a
configuration interfa
Hi,
I'd like to offeer my solution for 'multi layout' xkb maps.
I remind it allow to specify XkbLayout (and XkbVarinat) as list
of layout names that will be combined in one 'multi_layout'.
You can use use such list in XF86Config file
Option "XkbLayout" "us,il,ar"
or as an argument of t
Tzafrir Cohen wrote:
> Hi all
>
> Short summary: I see a problem with combining several layouts in the way
> "encouraged by XKB. An example to that problem is the question: how do I
> create a layout of "English(US)+Romanian+Hungarian"
I have almost completed new framework for XKB layouts and
On Thu, 21 Feb 2002, Ivan Pascal wrote:
> Tzafrir Cohen wrote:
>
> And the third part of work - we need rewrite all layouts map to make them
> 'single group' symbols maps. I have made few for testing but I don't dare
> to offer changes for all existent maps.
>
While on that:
Currently symbols
Tzafrir Cohen wrote:
> While on that:
>
> Currently symbols files also map some modifiers. e.g, from symbols/ru
>
> modifier_map Shift { Shift_L };
> modifier_map Lock { Caps_Lock, ISO_Lock };
> modifier_map Control{ Control_L };
> modifier_map Mod3 { Mode_switch };
>
> Are
Kaixo!
On Thu, Feb 21, 2002 at 04:38:27PM +0200, Tzafrir Cohen wrote:
> While on that:
>
> Currently symbols files also map some modifiers. e.g, from symbols/ru
>
> modifier_map Shift { Shift_L };
> modifier_map Lock { Caps_Lock, ISO_Lock };
> modifier_map Control{ Control_L };
Kaixo!
On Thu, Feb 21, 2002 at 06:39:02PM +0700, Ivan Pascal wrote:
> I have almost completed new framework for XKB layouts and thought of
> What I have done.
> First part is patches for a xkbcomp to make it recognize 'an explicit group
> specifying'. The modified xkbcomp understands as xkb
Pablo Saratxaga wrote:
> The problem with that is it breaks compatibility for all non-latin
> keyboards where two groups are used.
> Imagine some people has defined his keyboard just as "ru" or "th" etc.
> then he updates XFree86 and those files include only one group --> he
> is unable to type a
Pablo Saratxaga wrote:
> That would also avoid the need for a lot of variants, eg instead of
>
> "us(euro105)" it will be "us+euro105" (the difference between "us(default)"
> and "us(euro105)" is mainly the interpretation of the meaning of right Alt
> key and the extra "windows" keys etc. somethi
Kaixo!
On Mon, Feb 25, 2002 at 06:35:37PM +0700, Ivan Pascal wrote:
>
> Pablo Saratxaga wrote:
> > The problem with that is it breaks compatibility for all non-latin
> > keyboards where two groups are used.
> > Imagine some people has defined his keyboard just as "ru" or "th" etc.
> > then he up
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
11 matches
Mail list logo
