Re: Switching g-i from DirectFB to X11
On Thu, Feb 18, 2010 at 02:26:59PM +0100, Samuel Thibault wrote:
> Anton Zinoviev, le Tue 16 Feb 2010 23:58:06 +0200, a écrit :
> >
> > The only remaining problem that has to be fixed is in xkb-data - for
> > many layouts an US variant must be added so the users get it as option
> > in the first question.
>
> Some time ago, I had reported Bug 21046 – express that the us layout
> makes the majority in a bunch of countries
> https://bugs.freedesktop.org/show_bug.cgi?id=21046
>
> Is that what you have in mind?
Yes. Thank you for reporting this. :)
> It ended up with a question from Sergey about how to fix the layout
> names. I was unsure how to answer it so I left it apart. Maybe
> Christian has an idea?
This is how I would fix the nl keyboard:
--- nl 2010-02-18 17:30:07.579312728 +0200
+++ nl.new 2010-02-18 17:39:15.547313938 +0200
@@ -153,3 +153,14 @@
};
+partial alphanumeric_keys
+xkb_symbols "us" {
+
+ include "us(altgr-intl)"
+
+ name[Group1]= "Netherlands - USA International";
+
+ include "level3(ralt_switch)"
+
+};
+
I chose a variant without deadkeys in levels 1 and 2 (I suppose this is
what the people want). AltGr combinations can be used to produce
deadkeys. If this is not desirable then "ralt_alt" should be used
instead of "ralt_switch".
> > All other problems are either fixed or too difficult to fix.
>
> Do you have a list of the too difficult ones?
No. In my personal TODO list there is only one remaining thing:
currently c-s doesn't support some exotic configurations, such as two or
more compose-keys.
#532852 and #568645 are two wishlist bugs that are not related to the
installer and there is no urgency to fix them. However, #535834 is an
important one with no obvious solution - if the keyboard model is not
standard PC then some combinations are ivalid. In order to fix (at
least partialy) this problem, by default console-setup uses PC keyboard
model for macs too. This means that the default choice in keyboard
selection menu will be a non-mac layout.
The udebs are not tested (at all) but I don't expect bugs with difficult
fix here.
Anton Zinoviev
Reply to: