[New: openFATE 309487] Clean out X11 keyboard configuration in YaST
Feature added by: Jiří Suchomel (jsuchome) Feature #309487, revision 1 Title: Clean out X11 keyboard configuration in YaST Requested by: Jiří Suchomel (jsuchome) Developer: (Novell) Developer: (Novell) Description: Currently, 'yast2 keyboard' is using kind of strange way of determining which X11 keyboard layout to use. There's a map of internal YaST keyboard names, to which the list of kbd console maps is mapped (like, us.map.gz). Such console map is taken as a parameter for calling /usr/sbin/xkbctrl script, which returns the informations about corresponding X11 keyboard layout (usable for setxkbmap). One problem is that not for all languages, there's a sense to have console map, and because of this situation in YaST, we are using files like ar.map.gz, which are only links to us.map.gz. Other part is that the list of X11 keyboard layouts is part of sax2-tools package which we probably want to drop. New solution would mean that YaST has all the information currently provided by xkbctrl: either by building its own data structure (if there's no other application using it), or using a better way to get the data YaST needs to know. References: https://bugzilla.novell.com/show_bug.cgi?id=603950 https://bugzilla.novell.com/show_bug.cgi?id=601587 -- openSUSE Feature: https://features.opensuse.org/309487
Feature changed by: Stefan Dirsch (sndirsch) Feature #309487, revision 5 Title: Clean out X11 keyboard configuration in YaST - openSUSE-11.4: New + openSUSE-11.4: Rejected by Stefan Dirsch (sndirsch) + reject date: 2011-03-29 17:51:18 + reject reason: Obviously not being addressed. Priority Requester: Important Requested by: Jiří Suchomel (jsuchome) Engineering Manager: (Novell) Developer: (Novell) Developer: (Novell) Partner organization: openSUSE.org Description: Currently, 'yast2 keyboard' is using kind of strange way of determining which X11 keyboard layout to use. There's a map of internal YaST keyboard names, to which the list of kbd console maps is mapped (like, us.map.gz). Such console map is taken as a parameter for calling /usr/sbin/xkbctrl script, which returns the informations about corresponding X11 keyboard layout (usable for setxkbmap). One problem is that not for all languages, there's a sense to have console map, and because of this situation in YaST, we are using files like ar.map.gz, which are only links to us.map.gz. Other part is that the list of X11 keyboard layouts is part of sax2- tools package which we probably want to drop. New solution would mean that YaST has all the information currently provided by xkbctrl: either by building its own data structure (if there's no other application using it), or using a better way to get the data YaST needs to know. References: https://bugzilla.novell.com/show_bug.cgi?id=603950 https://bugzilla.novell.com/show_bug.cgi?id=601587 -- openSUSE Feature: https://features.opensuse.org/309487
Feature changed by: Jiří Suchomel (jsuchome) Feature #309487, revision 7 Title: Clean out X11 keyboard configuration in YaST openSUSE-11.4: Rejected by Stefan Dirsch (sndirsch) reject date: 2011-03-29 17:51:18 reject reason: Obviously not being addressed. Priority Requester: Important + openSUSE Distribution: Unconfirmed + Priority + Requester: Desirable Requested by: Jiří Suchomel (jsuchome) Partner organization: openSUSE.org Description: Currently, 'yast2 keyboard' is using kind of strange way of determining which X11 keyboard layout to use. There's a map of internal YaST keyboard names, to which the list of kbd console maps is mapped (like, us.map.gz). Such console map is taken as a parameter for calling /usr/sbin/xkbctrl script, which returns the informations about corresponding X11 keyboard layout (usable for setxkbmap). One problem is that not for all languages, there's a sense to have console map, and because of this situation in YaST, we are using files like ar.map.gz, which are only links to us.map.gz. Other part is that the list of X11 keyboard layouts is part of sax2- tools package which we probably want to drop. New solution would mean that YaST has all the information currently provided by xkbctrl: either by building its own data structure (if there's no other application using it), or using a better way to get the data YaST needs to know. References: https://bugzilla.novell.com/show_bug.cgi?id=603950 https://bugzilla.novell.com/show_bug.cgi?id=601587 -- openSUSE Feature: https://features.opensuse.org/309487
Feature changed by: Jiří Suchomel (jsuchome) Feature #309487, revision 8 Title: Clean out X11 keyboard configuration in YaST openSUSE-11.4: Rejected by Stefan Dirsch (sndirsch) reject date: 2011-03-29 17:51:18 reject reason: Obviously not being addressed. Priority Requester: Important openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Jiří Suchomel (jsuchome) Partner organization: openSUSE.org Description: Currently, 'yast2 keyboard' is using kind of strange way of determining which X11 keyboard layout to use. There's a map of internal YaST keyboard names, to which the list of kbd console maps is mapped (like, us.map.gz). Such console map is taken as a parameter for calling /usr/sbin/xkbctrl script, which returns the informations about corresponding X11 keyboard layout (usable for setxkbmap). One problem is that not for all languages, there's a sense to have console map, and because of this situation in YaST, we are using files like ar.map.gz, which are only links to us.map.gz. Other part is that the list of X11 keyboard layouts is part of sax2- tools package which we probably want to drop. New solution would mean that YaST has all the information currently provided by xkbctrl: either by building its own data structure (if there's no other application using it), or using a better way to get the data YaST needs to know. References: https://bugzilla.novell.com/show_bug.cgi?id=603950 https://bugzilla.novell.com/show_bug.cgi?id=601587 + Discussion: + #1: Jiří Suchomel (jsuchome) (2011-10-13 15:24:42) + Stefan, where does YaST get the info about which setxkbmap command to + call? -- openSUSE Feature: https://features.opensuse.org/309487
Feature changed by: Jiří Suchomel (jsuchome) Feature #309487, revision 9 Title: Clean out X11 keyboard configuration in YaST openSUSE-11.4: Rejected by Stefan Dirsch (sndirsch) reject date: 2011-03-29 17:51:18 reject reason: Obviously not being addressed. Priority Requester: Important openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Jiří Suchomel (jsuchome) Partner organization: openSUSE.org Description: Currently, 'yast2 keyboard' is using kind of strange way of determining which X11 keyboard layout to use. There's a map of internal YaST keyboard names, to which the list of kbd console maps is mapped (like, us.map.gz). Such console map is taken as a parameter for calling /usr/sbin/xkbctrl script, which returns the informations about corresponding X11 keyboard layout (usable for setxkbmap). One problem is that not for all languages, there's a sense to have console map, and because of this situation in YaST, we are using files like ar.map.gz, which are only links to us.map.gz. Other part is that the list of X11 keyboard layouts is part of sax2- tools package which we probably want to drop. New solution would mean that YaST has all the information currently provided by xkbctrl: either by building its own data structure (if there's no other application using it), or using a better way to get the data YaST needs to know. References: https://bugzilla.novell.com/show_bug.cgi?id=603950 https://bugzilla.novell.com/show_bug.cgi?id=601587 Discussion: #1: Jiří Suchomel (jsuchome) (2011-10-13 15:24:42) Stefan, where does YaST get the info about which setxkbmap command to call? + #2: Jiří Suchomel (jsuchome) (2011-10-14 11:34:50) + BTW, don't you know how other distros are doing it? Is there any common + mapping from locale (de_DE) to console key map and X11 keyboard map? + Actually, if we'd create some new file for it, I'd still more like to + have it not inside YaST filesystem subtree, so it is easily available + to potential other applications. -- openSUSE Feature: https://features.opensuse.org/309487
Feature changed by: Stefan Dirsch (sndirsch) Feature #309487, revision 10 Title: Clean out X11 keyboard configuration in YaST openSUSE-11.4: Rejected by Stefan Dirsch (sndirsch) reject date: 2011-03-29 17:51:18 reject reason: Obviously not being addressed. Priority Requester: Important openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Jiří Suchomel (jsuchome) Partner organization: openSUSE.org Description: Currently, 'yast2 keyboard' is using kind of strange way of determining which X11 keyboard layout to use. There's a map of internal YaST keyboard names, to which the list of kbd console maps is mapped (like, us.map.gz). Such console map is taken as a parameter for calling /usr/sbin/xkbctrl script, which returns the informations about corresponding X11 keyboard layout (usable for setxkbmap). One problem is that not for all languages, there's a sense to have console map, and because of this situation in YaST, we are using files like ar.map.gz, which are only links to us.map.gz. Other part is that the list of X11 keyboard layouts is part of sax2- tools package which we probably want to drop. New solution would mean that YaST has all the information currently provided by xkbctrl: either by building its own data structure (if there's no other application using it), or using a better way to get the data YaST needs to know. References: https://bugzilla.novell.com/show_bug.cgi?id=603950 https://bugzilla.novell.com/show_bug.cgi?id=601587 Discussion: #1: Jiří Suchomel (jsuchome) (2011-10-13 15:24:42) Stefan, where does YaST get the info about which setxkbmap command to call? + #3: Stefan Dirsch (sndirsch) (2011-10-14 11:41:44) (reply to #1) + The information in /etc/X11/xdm/Keyboard.map can be used for a new + start. #2: Jiří Suchomel (jsuchome) (2011-10-14 11:34:50) BTW, don't you know how other distros are doing it? Is there any common mapping from locale (de_DE) to console key map and X11 keyboard map? Actually, if we'd create some new file for it, I'd still more like to have it not inside YaST filesystem subtree, so it is easily available to potential other applications. -- openSUSE Feature: https://features.opensuse.org/309487
Feature changed by: Stefan Dirsch (sndirsch) Feature #309487, revision 11 Title: Clean out X11 keyboard configuration in YaST openSUSE-11.4: Rejected by Stefan Dirsch (sndirsch) reject date: 2011-03-29 17:51:18 reject reason: Obviously not being addressed. Priority Requester: Important openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Jiří Suchomel (jsuchome) Partner organization: openSUSE.org Description: Currently, 'yast2 keyboard' is using kind of strange way of determining which X11 keyboard layout to use. There's a map of internal YaST keyboard names, to which the list of kbd console maps is mapped (like, us.map.gz). Such console map is taken as a parameter for calling /usr/sbin/xkbctrl script, which returns the informations about corresponding X11 keyboard layout (usable for setxkbmap). One problem is that not for all languages, there's a sense to have console map, and because of this situation in YaST, we are using files like ar.map.gz, which are only links to us.map.gz. Other part is that the list of X11 keyboard layouts is part of sax2- tools package which we probably want to drop. New solution would mean that YaST has all the information currently provided by xkbctrl: either by building its own data structure (if there's no other application using it), or using a better way to get the data YaST needs to know. References: https://bugzilla.novell.com/show_bug.cgi?id=603950 https://bugzilla.novell.com/show_bug.cgi?id=601587 Discussion: #1: Jiří Suchomel (jsuchome) (2011-10-13 15:24:42) Stefan, where does YaST get the info about which setxkbmap command to call? #3: Stefan Dirsch (sndirsch) (2011-10-14 11:41:44) (reply to #1) The information in /etc/X11/xdm/Keyboard.map can be used for a new start. #2: Jiří Suchomel (jsuchome) (2011-10-14 11:34:50) BTW, don't you know how other distros are doing it? Is there any common mapping from locale (de_DE) to console key map and X11 keyboard map? Actually, if we'd create some new file for it, I'd still more like to have it not inside YaST filesystem subtree, so it is easily available to potential other applications. + #4: Stefan Dirsch (sndirsch) (2011-10-14 11:52:09) (reply to #2) + I don't know how other distros handle this. You would like to figure it + out? Please go ahead. I always thought YaST is our config tool. + I would go for a config file/configuration, which is read by the usual + desktops like KDE, Gnome, Xfce, etc to use this keyboard setting by + default (global keyboard configuration) unless the user choses a + different one. And that way finally get rid of this /etc/X11/xorg.conf. + d/90-keytable.conf snippet created by /etc/X11/xdm/keytable. And yes, + this will no longer cover the twm/fvwm2 user. -- openSUSE Feature: https://features.opensuse.org/309487
Feature changed by: Jiří Suchomel (jsuchome) Feature #309487, revision 12 Title: Clean out X11 keyboard configuration in YaST openSUSE-11.4: Rejected by Stefan Dirsch (sndirsch) reject date: 2011-03-29 17:51:18 reject reason: Obviously not being addressed. Priority Requester: Important openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Jiří Suchomel (jsuchome) Partner organization: openSUSE.org Description: Currently, 'yast2 keyboard' is using kind of strange way of determining which X11 keyboard layout to use. There's a map of internal YaST keyboard names, to which the list of kbd console maps is mapped (like, us.map.gz). Such console map is taken as a parameter for calling /usr/sbin/xkbctrl script, which returns the informations about corresponding X11 keyboard layout (usable for setxkbmap). One problem is that not for all languages, there's a sense to have console map, and because of this situation in YaST, we are using files like ar.map.gz, which are only links to us.map.gz. Other part is that the list of X11 keyboard layouts is part of sax2- tools package which we probably want to drop. New solution would mean that YaST has all the information currently provided by xkbctrl: either by building its own data structure (if there's no other application using it), or using a better way to get the data YaST needs to know. References: https://bugzilla.novell.com/show_bug.cgi?id=603950 https://bugzilla.novell.com/show_bug.cgi?id=601587 + https://bugzilla.novell.com/show_bug.cgi?id=725468 Discussion: #1: Jiří Suchomel (jsuchome) (2011-10-13 15:24:42) Stefan, where does YaST get the info about which setxkbmap command to call? #3: Stefan Dirsch (sndirsch) (2011-10-14 11:41:44) (reply to #1) The information in /etc/X11/xdm/Keyboard.map can be used for a new start. #2: Jiří Suchomel (jsuchome) (2011-10-14 11:34:50) BTW, don't you know how other distros are doing it? Is there any common mapping from locale (de_DE) to console key map and X11 keyboard map? Actually, if we'd create some new file for it, I'd still more like to have it not inside YaST filesystem subtree, so it is easily available to potential other applications. #4: Stefan Dirsch (sndirsch) (2011-10-14 11:52:09) (reply to #2) I don't know how other distros handle this. You would like to figure it out? Please go ahead. I always thought YaST is our config tool. I would go for a config file/configuration, which is read by the usual desktops like KDE, Gnome, Xfce, etc to use this keyboard setting by default (global keyboard configuration) unless the user choses a different one. And that way finally get rid of this /etc/X11/xorg.conf. d/90-keytable.conf snippet created by /etc/X11/xdm/keytable. And yes, this will no longer cover the twm/fvwm2 user. -- openSUSE Feature: https://features.opensuse.org/309487
Feature changed by: Jiří Suchomel (jsuchome) Feature #309487, revision 13 Title: Clean out X11 keyboard configuration in YaST openSUSE-11.4: Rejected by Stefan Dirsch (sndirsch) reject date: 2011-03-29 17:51:18 reject reason: Obviously not being addressed. Priority Requester: Important openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Jiří Suchomel (jsuchome) Partner organization: openSUSE.org Description: Currently, 'yast2 keyboard' is using kind of strange way of determining which X11 keyboard layout to use. There's a map of internal YaST keyboard names, to which the list of kbd console maps is mapped (like, us.map.gz). Such console map is taken as a parameter for calling /usr/sbin/xkbctrl script, which returns the informations about corresponding X11 keyboard layout (usable for setxkbmap). One problem is that not for all languages, there's a sense to have console map, and because of this situation in YaST, we are using files like ar.map.gz, which are only links to us.map.gz. Other part is that the list of X11 keyboard layouts is part of sax2- tools package which we probably want to drop. New solution would mean that YaST has all the information currently provided by xkbctrl: either by building its own data structure (if there's no other application using it), or using a better way to get the data YaST needs to know. References: https://bugzilla.novell.com/show_bug.cgi?id=603950 https://bugzilla.novell.com/show_bug.cgi?id=601587 https://bugzilla.novell.com/show_bug.cgi?id=725468 Discussion: #1: Jiří Suchomel (jsuchome) (2011-10-13 15:24:42) Stefan, where does YaST get the info about which setxkbmap command to call? #3: Stefan Dirsch (sndirsch) (2011-10-14 11:41:44) (reply to #1) The information in /etc/X11/xdm/Keyboard.map can be used for a new start. #2: Jiří Suchomel (jsuchome) (2011-10-14 11:34:50) BTW, don't you know how other distros are doing it? Is there any common mapping from locale (de_DE) to console key map and X11 keyboard map? Actually, if we'd create some new file for it, I'd still more like to have it not inside YaST filesystem subtree, so it is easily available to potential other applications. #4: Stefan Dirsch (sndirsch) (2011-10-14 11:52:09) (reply to #2) I don't know how other distros handle this. You would like to figure it out? Please go ahead. I always thought YaST is our config tool. I would go for a config file/configuration, which is read by the usual desktops like KDE, Gnome, Xfce, etc to use this keyboard setting by default (global keyboard configuration) unless the user choses a different one. And that way finally get rid of this /etc/X11/xorg.conf. d/90-keytable.conf snippet created by /etc/X11/xdm/keytable. And yes, this will no longer cover the twm/fvwm2 user. + #5: Jiří Suchomel (jsuchome) (2012-01-05 11:07:35) + 1. So, YaST should offer all X11 layouts from start: where can I find + the list of them? I assume there's a list, which is used buy KDE/GNOME + tools. I think we should not use only the subset from + /etc/X11/xdm/Keyboard.map. + 2. YaST needs to determine which layout to used as defalt, based on + user language during the installation. But this could stay YaST + internal, as it is relevant to installation only. + 3. Based on selected X11 layout, YaST should set also console keyboard. + The mapping of X11-> console could be taken from current + /etc/X11/xdm/Keyboard.map (it does not cover all X11 layouts, but that + is fine) and could probably stay internal in YaST. Or do you think it + makes sense to make it public for any other (desktop) applications? + 4. The variable in KEYTABLE in /etc/sysconfig/keyboard could probably + stay with current meaning. + 5. We probably need to save X11 keyboard information saved somewhere + (esp. during installation, when setxkbmap call is not available), and + this info would be read by desktops to apply the layout, right? Seems + like such config should contain all options needed for setxkbmap so + other conversions are not needed. What do you think, could use + /etc/sysconfig/keyboard for that? With the values like X11_LAYOUT, + X11_VARIANT etc.? -- openSUSE Feature: https://features.opensuse.org/309487
Feature changed by: Stefan Dirsch (sndirsch) Feature #309487, revision 15 Title: Clean out X11 keyboard configuration in YaST openSUSE-11.4: Rejected by Stefan Dirsch (sndirsch) reject date: 2011-03-29 17:51:18 reject reason: Obviously not being addressed. Priority Requester: Important openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Jiří Suchomel (jsuchome) Partner organization: openSUSE.org Description: Currently, 'yast2 keyboard' is using kind of strange way of determining which X11 keyboard layout to use. There's a map of internal YaST keyboard names, to which the list of kbd console maps is mapped (like, us.map.gz). Such console map is taken as a parameter for calling /usr/sbin/xkbctrl script, which returns the informations about corresponding X11 keyboard layout (usable for setxkbmap). One problem is that not for all languages, there's a sense to have console map, and because of this situation in YaST, we are using files like ar.map.gz, which are only links to us.map.gz. Other part is that the list of X11 keyboard layouts is part of sax2- tools package which we probably want to drop. New solution would mean that YaST has all the information currently provided by xkbctrl: either by building its own data structure (if there's no other application using it), or using a better way to get the data YaST needs to know. References: https://bugzilla.novell.com/show_bug.cgi?id=603950 https://bugzilla.novell.com/show_bug.cgi?id=601587 https://bugzilla.novell.com/show_bug.cgi?id=725468 Discussion: #1: Jiří Suchomel (jsuchome) (2011-10-13 15:24:42) Stefan, where does YaST get the info about which setxkbmap command to call? #3: Stefan Dirsch (sndirsch) (2011-10-14 11:41:44) (reply to #1) The information in /etc/X11/xdm/Keyboard.map can be used for a new start. #2: Jiří Suchomel (jsuchome) (2011-10-14 11:34:50) BTW, don't you know how other distros are doing it? Is there any common mapping from locale (de_DE) to console key map and X11 keyboard map? Actually, if we'd create some new file for it, I'd still more like to have it not inside YaST filesystem subtree, so it is easily available to potential other applications. #4: Stefan Dirsch (sndirsch) (2011-10-14 11:52:09) (reply to #2) I don't know how other distros handle this. You would like to figure it out? Please go ahead. I always thought YaST is our config tool. I would go for a config file/configuration, which is read by the usual desktops like KDE, Gnome, Xfce, etc to use this keyboard setting by default (global keyboard configuration) unless the user choses a different one. And that way finally get rid of this /etc/X11/xorg.conf. d/90-keytable.conf snippet created by /etc/X11/xdm/keytable. And yes, this will no longer cover the twm/fvwm2 user. #5: Jiří Suchomel (jsuchome) (2012-01-05 11:07:35) 1. So, YaST should offer all X11 layouts from start: where can I find the list of them? I assume there's a list, which is used buy KDE/GNOME tools. I think we should not use only the subset from /etc/X11/xdm/Keyboard.map. 2. YaST needs to determine which layout to used as defalt, based on user language during the installation. But this could stay YaST internal, as it is relevant to installation only. 3. Based on selected X11 layout, YaST should set also console keyboard. The mapping of X11-> console could be taken from current /etc/X11/xdm/Keyboard.map (it does not cover all X11 layouts, but that is fine) and could probably stay internal in YaST. Or do you think it makes sense to make it public for any other (desktop) applications? 4. The variable in KEYTABLE in /etc/sysconfig/keyboard could probably stay with current meaning. 5. We probably need to save X11 keyboard information saved somewhere (esp. during installation, when setxkbmap call is not available), and this info would be read by desktops to apply the layout, right? Seems like such config should contain all options needed for setxkbmap so other conversions are not needed. What do you think, could use /etc/sysconfig/keyboard for that? With the values like X11_LAYOUT, X11_VARIANT etc.? + #6: Stefan Dirsch (sndirsch) (2012-01-05 12:28:04) (reply to #5) + @1: I'm not sure whether KDE/GNOME tools use a static list for this or + if they figure this out on-the-fly via libxkb and how. Please ask our + KDE/GNOME developers. They should know better than me. @2: I agree. + Default should depend on the language. Unless we can detect the + keyboard language ... @3: I agree. I don't think desktop applications + are interested in Linux console keyboard layout. :-) @4: Sure. I agree. + This variable can stay with the current meaning. + @5: Basically I agree, but I wouldn't split this into several options + (of course YaST internal you do this). Just all options for the + setxkbmap command in one string. -- openSUSE Feature: https://features.opensuse.org/309487
Feature changed by: Jiří Suchomel (jsuchome) Feature #309487, revision 16 Title: Clean out X11 keyboard configuration in YaST openSUSE-11.4: Rejected by Stefan Dirsch (sndirsch) reject date: 2011-03-29 17:51:18 reject reason: Obviously not being addressed. Priority Requester: Important openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Jiří Suchomel (jsuchome) Partner organization: openSUSE.org Description: Currently, 'yast2 keyboard' is using kind of strange way of determining which X11 keyboard layout to use. There's a map of internal YaST keyboard names, to which the list of kbd console maps is mapped (like, us.map.gz). Such console map is taken as a parameter for calling /usr/sbin/xkbctrl script, which returns the informations about corresponding X11 keyboard layout (usable for setxkbmap). One problem is that not for all languages, there's a sense to have console map, and because of this situation in YaST, we are using files like ar.map.gz, which are only links to us.map.gz. Other part is that the list of X11 keyboard layouts is part of sax2- tools package which we probably want to drop. New solution would mean that YaST has all the information currently provided by xkbctrl: either by building its own data structure (if there's no other application using it), or using a better way to get the data YaST needs to know. References: https://bugzilla.novell.com/show_bug.cgi?id=603950 https://bugzilla.novell.com/show_bug.cgi?id=601587 https://bugzilla.novell.com/show_bug.cgi?id=725468 Discussion: #1: Jiří Suchomel (jsuchome) (2011-10-13 15:24:42) Stefan, where does YaST get the info about which setxkbmap command to call? #3: Stefan Dirsch (sndirsch) (2011-10-14 11:41:44) (reply to #1) The information in /etc/X11/xdm/Keyboard.map can be used for a new start. #2: Jiří Suchomel (jsuchome) (2011-10-14 11:34:50) BTW, don't you know how other distros are doing it? Is there any common mapping from locale (de_DE) to console key map and X11 keyboard map? Actually, if we'd create some new file for it, I'd still more like to have it not inside YaST filesystem subtree, so it is easily available to potential other applications. #4: Stefan Dirsch (sndirsch) (2011-10-14 11:52:09) (reply to #2) I don't know how other distros handle this. You would like to figure it out? Please go ahead. I always thought YaST is our config tool. I would go for a config file/configuration, which is read by the usual desktops like KDE, Gnome, Xfce, etc to use this keyboard setting by default (global keyboard configuration) unless the user choses a different one. And that way finally get rid of this /etc/X11/xorg.conf. d/90-keytable.conf snippet created by /etc/X11/xdm/keytable. And yes, this will no longer cover the twm/fvwm2 user. #5: Jiří Suchomel (jsuchome) (2012-01-05 11:07:35) 1. So, YaST should offer all X11 layouts from start: where can I find the list of them? I assume there's a list, which is used buy KDE/GNOME tools. I think we should not use only the subset from /etc/X11/xdm/Keyboard.map. 2. YaST needs to determine which layout to used as defalt, based on user language during the installation. But this could stay YaST internal, as it is relevant to installation only. 3. Based on selected X11 layout, YaST should set also console keyboard. The mapping of X11-> console could be taken from current /etc/X11/xdm/Keyboard.map (it does not cover all X11 layouts, but that is fine) and could probably stay internal in YaST. Or do you think it makes sense to make it public for any other (desktop) applications? 4. The variable in KEYTABLE in /etc/sysconfig/keyboard could probably stay with current meaning. 5. We probably need to save X11 keyboard information saved somewhere (esp. during installation, when setxkbmap call is not available), and this info would be read by desktops to apply the layout, right? Seems like such config should contain all options needed for setxkbmap so other conversions are not needed. What do you think, could use /etc/sysconfig/keyboard for that? With the values like X11_LAYOUT, X11_VARIANT etc.? #6: Stefan Dirsch (sndirsch) (2012-01-05 12:28:04) (reply to #5) @1: I'm not sure whether KDE/GNOME tools use a static list for this or if they figure this out on-the-fly via libxkb and how. Please ask our KDE/GNOME developers. They should know better than me. @2: I agree. Default should depend on the language. Unless we can detect the keyboard language ... @3: I agree. I don't think desktop applications are interested in Linux console keyboard layout. :-) @4: Sure. I agree. This variable can stay with the current meaning. @5: Basically I agree, but I wouldn't split this into several options (of course YaST internal you do this). Just all options for the setxkbmap command in one string. + #7: Jiří Suchomel (jsuchome) (2012-01-09 14:11:59) + Tested Fedora 16: installer offers more layouts than we do, but I think + not all of X11 available. Console keyboard does not seem to be + configured. /etc/sysconfig/keyboard contains the keys KEYTABLE, MODEL, + LAYOUT and VARIANT, which is close to our proposal. -- openSUSE Feature: https://features.opensuse.org/309487
Feature changed by: Jiří Suchomel (jsuchome) Feature #309487, revision 17 Title: Clean out X11 keyboard configuration in YaST openSUSE-11.4: Rejected by Stefan Dirsch (sndirsch) reject date: 2011-03-29 17:51:18 reject reason: Obviously not being addressed. Priority Requester: Important openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Jiří Suchomel (jsuchome) Partner organization: openSUSE.org Description: Currently, 'yast2 keyboard' is using kind of strange way of determining which X11 keyboard layout to use. There's a map of internal YaST keyboard names, to which the list of kbd console maps is mapped (like, us.map.gz). Such console map is taken as a parameter for calling /usr/sbin/xkbctrl script, which returns the informations about corresponding X11 keyboard layout (usable for setxkbmap). One problem is that not for all languages, there's a sense to have console map, and because of this situation in YaST, we are using files like ar.map.gz, which are only links to us.map.gz. Other part is that the list of X11 keyboard layouts is part of sax2- tools package which we probably want to drop. New solution would mean that YaST has all the information currently provided by xkbctrl: either by building its own data structure (if there's no other application using it), or using a better way to get the data YaST needs to know. References: https://bugzilla.novell.com/show_bug.cgi?id=603950 https://bugzilla.novell.com/show_bug.cgi?id=601587 https://bugzilla.novell.com/show_bug.cgi?id=725468 Discussion: #1: Jiří Suchomel (jsuchome) (2011-10-13 15:24:42) Stefan, where does YaST get the info about which setxkbmap command to call? #3: Stefan Dirsch (sndirsch) (2011-10-14 11:41:44) (reply to #1) The information in /etc/X11/xdm/Keyboard.map can be used for a new start. #2: Jiří Suchomel (jsuchome) (2011-10-14 11:34:50) BTW, don't you know how other distros are doing it? Is there any common mapping from locale (de_DE) to console key map and X11 keyboard map? Actually, if we'd create some new file for it, I'd still more like to have it not inside YaST filesystem subtree, so it is easily available to potential other applications. #4: Stefan Dirsch (sndirsch) (2011-10-14 11:52:09) (reply to #2) I don't know how other distros handle this. You would like to figure it out? Please go ahead. I always thought YaST is our config tool. I would go for a config file/configuration, which is read by the usual desktops like KDE, Gnome, Xfce, etc to use this keyboard setting by default (global keyboard configuration) unless the user choses a different one. And that way finally get rid of this /etc/X11/xorg.conf. d/90-keytable.conf snippet created by /etc/X11/xdm/keytable. And yes, this will no longer cover the twm/fvwm2 user. #5: Jiří Suchomel (jsuchome) (2012-01-05 11:07:35) 1. So, YaST should offer all X11 layouts from start: where can I find the list of them? I assume there's a list, which is used buy KDE/GNOME tools. I think we should not use only the subset from /etc/X11/xdm/Keyboard.map. 2. YaST needs to determine which layout to used as defalt, based on user language during the installation. But this could stay YaST internal, as it is relevant to installation only. 3. Based on selected X11 layout, YaST should set also console keyboard. The mapping of X11-> console could be taken from current /etc/X11/xdm/Keyboard.map (it does not cover all X11 layouts, but that is fine) and could probably stay internal in YaST. Or do you think it makes sense to make it public for any other (desktop) applications? 4. The variable in KEYTABLE in /etc/sysconfig/keyboard could probably stay with current meaning. 5. We probably need to save X11 keyboard information saved somewhere (esp. during installation, when setxkbmap call is not available), and this info would be read by desktops to apply the layout, right? Seems like such config should contain all options needed for setxkbmap so other conversions are not needed. What do you think, could use /etc/sysconfig/keyboard for that? With the values like X11_LAYOUT, X11_VARIANT etc.? #6: Stefan Dirsch (sndirsch) (2012-01-05 12:28:04) (reply to #5) @1: I'm not sure whether KDE/GNOME tools use a static list for this or if they figure this out on-the-fly via libxkb and how. Please ask our KDE/GNOME developers. They should know better than me. @2: I agree. Default should depend on the language. Unless we can detect the keyboard language ... @3: I agree. I don't think desktop applications are interested in Linux console keyboard layout. :-) @4: Sure. I agree. This variable can stay with the current meaning. @5: Basically I agree, but I wouldn't split this into several options (of course YaST internal you do this). Just all options for the setxkbmap command in one string. #7: Jiří Suchomel (jsuchome) (2012-01-09 14:11:59) Tested Fedora 16: installer offers more layouts than we do, but I think not all of X11 available. Console keyboard does not seem to be configured. /etc/sysconfig/keyboard contains the keys KEYTABLE, MODEL, LAYOUT and VARIANT, which is close to our proposal. + #8: Jiří Suchomel (jsuchome) (2012-01-09 14:40:57) + Ubuntu installer seems to offer full X11 layouts support. After + installation, console keyboard is probably set as well, but not console + font, which results in unusable situation (tested CZ layout) -- openSUSE Feature: https://features.opensuse.org/309487
Feature changed by: Jiří Suchomel (jsuchome) Feature #309487, revision 18 Title: Clean out X11 keyboard configuration in YaST openSUSE-11.4: Rejected by Stefan Dirsch (sndirsch) reject date: 2011-03-29 17:51:18 reject reason: Obviously not being addressed. Priority Requester: Important openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Jiří Suchomel (jsuchome) Partner organization: openSUSE.org Description: Currently, 'yast2 keyboard' is using kind of strange way of determining which X11 keyboard layout to use. There's a map of internal YaST keyboard names, to which the list of kbd console maps is mapped (like, us.map.gz). Such console map is taken as a parameter for calling /usr/sbin/xkbctrl script, which returns the informations about corresponding X11 keyboard layout (usable for setxkbmap). One problem is that not for all languages, there's a sense to have console map, and because of this situation in YaST, we are using files like ar.map.gz, which are only links to us.map.gz. Other part is that the list of X11 keyboard layouts is part of sax2- tools package which we probably want to drop. New solution would mean that YaST has all the information currently provided by xkbctrl: either by building its own data structure (if there's no other application using it), or using a better way to get the data YaST needs to know. References: https://bugzilla.novell.com/show_bug.cgi?id=603950 https://bugzilla.novell.com/show_bug.cgi?id=601587 https://bugzilla.novell.com/show_bug.cgi?id=725468 Discussion: #1: Jiří Suchomel (jsuchome) (2011-10-13 15:24:42) Stefan, where does YaST get the info about which setxkbmap command to call? #3: Stefan Dirsch (sndirsch) (2011-10-14 11:41:44) (reply to #1) The information in /etc/X11/xdm/Keyboard.map can be used for a new start. #2: Jiří Suchomel (jsuchome) (2011-10-14 11:34:50) BTW, don't you know how other distros are doing it? Is there any common mapping from locale (de_DE) to console key map and X11 keyboard map? Actually, if we'd create some new file for it, I'd still more like to have it not inside YaST filesystem subtree, so it is easily available to potential other applications. #4: Stefan Dirsch (sndirsch) (2011-10-14 11:52:09) (reply to #2) I don't know how other distros handle this. You would like to figure it out? Please go ahead. I always thought YaST is our config tool. I would go for a config file/configuration, which is read by the usual desktops like KDE, Gnome, Xfce, etc to use this keyboard setting by default (global keyboard configuration) unless the user choses a different one. And that way finally get rid of this /etc/X11/xorg.conf. d/90-keytable.conf snippet created by /etc/X11/xdm/keytable. And yes, this will no longer cover the twm/fvwm2 user. #5: Jiří Suchomel (jsuchome) (2012-01-05 11:07:35) 1. So, YaST should offer all X11 layouts from start: where can I find the list of them? I assume there's a list, which is used buy KDE/GNOME tools. I think we should not use only the subset from /etc/X11/xdm/Keyboard.map. 2. YaST needs to determine which layout to used as defalt, based on user language during the installation. But this could stay YaST internal, as it is relevant to installation only. 3. Based on selected X11 layout, YaST should set also console keyboard. The mapping of X11-> console could be taken from current /etc/X11/xdm/Keyboard.map (it does not cover all X11 layouts, but that is fine) and could probably stay internal in YaST. Or do you think it makes sense to make it public for any other (desktop) applications? 4. The variable in KEYTABLE in /etc/sysconfig/keyboard could probably stay with current meaning. 5. We probably need to save X11 keyboard information saved somewhere (esp. during installation, when setxkbmap call is not available), and this info would be read by desktops to apply the layout, right? Seems like such config should contain all options needed for setxkbmap so other conversions are not needed. What do you think, could use /etc/sysconfig/keyboard for that? With the values like X11_LAYOUT, X11_VARIANT etc.? #6: Stefan Dirsch (sndirsch) (2012-01-05 12:28:04) (reply to #5) @1: I'm not sure whether KDE/GNOME tools use a static list for this or if they figure this out on-the-fly via libxkb and how. Please ask our KDE/GNOME developers. They should know better than me. @2: I agree. Default should depend on the language. Unless we can detect the keyboard language ... @3: I agree. I don't think desktop applications are interested in Linux console keyboard layout. :-) @4: Sure. I agree. This variable can stay with the current meaning. @5: Basically I agree, but I wouldn't split this into several options (of course YaST internal you do this). Just all options for the setxkbmap command in one string. #7: Jiří Suchomel (jsuchome) (2012-01-09 14:11:59) Tested Fedora 16: installer offers more layouts than we do, but I think not all of X11 available. Console keyboard does not seem to be configured. /etc/sysconfig/keyboard contains the keys KEYTABLE, MODEL, LAYOUT and VARIANT, which is close to our proposal. #8: Jiří Suchomel (jsuchome) (2012-01-09 14:40:57) Ubuntu installer seems to offer full X11 layouts support. After installation, console keyboard is probably set as well, but not console font, which results in unusable situation (tested CZ layout) + #9: Jiří Suchomel (jsuchome) (2012-01-10 11:30:34) + Jiri, what is your point of view? -- openSUSE Feature: https://features.opensuse.org/309487
Feature changed by: Jiri Srain (jsrain) Feature #309487, revision 19 Title: Clean out X11 keyboard configuration in YaST openSUSE-11.4: Rejected by Stefan Dirsch (sndirsch) reject date: 2011-03-29 17:51:18 reject reason: Obviously not being addressed. Priority Requester: Important openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Jiří Suchomel (jsuchome) Partner organization: openSUSE.org Description: Currently, 'yast2 keyboard' is using kind of strange way of determining which X11 keyboard layout to use. There's a map of internal YaST keyboard names, to which the list of kbd console maps is mapped (like, us.map.gz). Such console map is taken as a parameter for calling /usr/sbin/xkbctrl script, which returns the informations about corresponding X11 keyboard layout (usable for setxkbmap). One problem is that not for all languages, there's a sense to have console map, and because of this situation in YaST, we are using files like ar.map.gz, which are only links to us.map.gz. Other part is that the list of X11 keyboard layouts is part of sax2- tools package which we probably want to drop. New solution would mean that YaST has all the information currently provided by xkbctrl: either by building its own data structure (if there's no other application using it), or using a better way to get the data YaST needs to know. References: https://bugzilla.novell.com/show_bug.cgi?id=603950 https://bugzilla.novell.com/show_bug.cgi?id=601587 https://bugzilla.novell.com/show_bug.cgi?id=725468 Discussion: #1: Jiří Suchomel (jsuchome) (2011-10-13 15:24:42) Stefan, where does YaST get the info about which setxkbmap command to call? #3: Stefan Dirsch (sndirsch) (2011-10-14 11:41:44) (reply to #1) The information in /etc/X11/xdm/Keyboard.map can be used for a new start. #2: Jiří Suchomel (jsuchome) (2011-10-14 11:34:50) BTW, don't you know how other distros are doing it? Is there any common mapping from locale (de_DE) to console key map and X11 keyboard map? Actually, if we'd create some new file for it, I'd still more like to have it not inside YaST filesystem subtree, so it is easily available to potential other applications. #4: Stefan Dirsch (sndirsch) (2011-10-14 11:52:09) (reply to #2) I don't know how other distros handle this. You would like to figure it out? Please go ahead. I always thought YaST is our config tool. I would go for a config file/configuration, which is read by the usual desktops like KDE, Gnome, Xfce, etc to use this keyboard setting by default (global keyboard configuration) unless the user choses a different one. And that way finally get rid of this /etc/X11/xorg.conf. d/90-keytable.conf snippet created by /etc/X11/xdm/keytable. And yes, this will no longer cover the twm/fvwm2 user. #5: Jiří Suchomel (jsuchome) (2012-01-05 11:07:35) 1. So, YaST should offer all X11 layouts from start: where can I find the list of them? I assume there's a list, which is used buy KDE/GNOME tools. I think we should not use only the subset from /etc/X11/xdm/Keyboard.map. 2. YaST needs to determine which layout to used as defalt, based on user language during the installation. But this could stay YaST internal, as it is relevant to installation only. 3. Based on selected X11 layout, YaST should set also console keyboard. The mapping of X11-> console could be taken from current /etc/X11/xdm/Keyboard.map (it does not cover all X11 layouts, but that is fine) and could probably stay internal in YaST. Or do you think it makes sense to make it public for any other (desktop) applications? 4. The variable in KEYTABLE in /etc/sysconfig/keyboard could probably stay with current meaning. 5. We probably need to save X11 keyboard information saved somewhere (esp. during installation, when setxkbmap call is not available), and this info would be read by desktops to apply the layout, right? Seems like such config should contain all options needed for setxkbmap so other conversions are not needed. What do you think, could use /etc/sysconfig/keyboard for that? With the values like X11_LAYOUT, X11_VARIANT etc.? #6: Stefan Dirsch (sndirsch) (2012-01-05 12:28:04) (reply to #5) @1: I'm not sure whether KDE/GNOME tools use a static list for this or if they figure this out on-the-fly via libxkb and how. Please ask our KDE/GNOME developers. They should know better than me. @2: I agree. Default should depend on the language. Unless we can detect the keyboard language ... @3: I agree. I don't think desktop applications are interested in Linux console keyboard layout. :-) @4: Sure. I agree. This variable can stay with the current meaning. @5: Basically I agree, but I wouldn't split this into several options (of course YaST internal you do this). Just all options for the setxkbmap command in one string. #7: Jiří Suchomel (jsuchome) (2012-01-09 14:11:59) Tested Fedora 16: installer offers more layouts than we do, but I think not all of X11 available. Console keyboard does not seem to be configured. /etc/sysconfig/keyboard contains the keys KEYTABLE, MODEL, LAYOUT and VARIANT, which is close to our proposal. #8: Jiří Suchomel (jsuchome) (2012-01-09 14:40:57) Ubuntu installer seems to offer full X11 layouts support. After installation, console keyboard is probably set as well, but not console font, which results in unusable situation (tested CZ layout) #9: Jiří Suchomel (jsuchome) (2012-01-10 11:30:34) Jiri, what is your point of view? + #10: Jiri Srain (jsrain) (2012-01-19 09:59:05) (reply to #9) + I don't really see the value of this feature. I understand that there + is a burden of maintaining a conversion table between console and X11 + layouts, but I don't see the alternative (moving it between packages + does not really help). + How often are we asked to add another layout? -- openSUSE Feature: https://features.opensuse.org/309487
Feature changed by: Diggory Hardy (d_hardy) Feature #309487, revision 20 Title: Clean out X11 keyboard configuration in YaST openSUSE-11.4: Rejected by Stefan Dirsch (sndirsch) reject date: 2011-03-29 17:51:18 reject reason: Obviously not being addressed. Priority Requester: Important openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Jiří Suchomel (jsuchome) Partner organization: openSUSE.org Description: Currently, 'yast2 keyboard' is using kind of strange way of determining which X11 keyboard layout to use. There's a map of internal YaST keyboard names, to which the list of kbd console maps is mapped (like, us.map.gz). Such console map is taken as a parameter for calling /usr/sbin/xkbctrl script, which returns the informations about corresponding X11 keyboard layout (usable for setxkbmap). One problem is that not for all languages, there's a sense to have console map, and because of this situation in YaST, we are using files like ar.map.gz, which are only links to us.map.gz. Other part is that the list of X11 keyboard layouts is part of sax2- tools package which we probably want to drop. New solution would mean that YaST has all the information currently provided by xkbctrl: either by building its own data structure (if there's no other application using it), or using a better way to get the data YaST needs to know. References: https://bugzilla.novell.com/show_bug.cgi?id=603950 https://bugzilla.novell.com/show_bug.cgi?id=601587 https://bugzilla.novell.com/show_bug.cgi?id=725468 Discussion: #1: Jiří Suchomel (jsuchome) (2011-10-13 15:24:42) Stefan, where does YaST get the info about which setxkbmap command to call? #3: Stefan Dirsch (sndirsch) (2011-10-14 11:41:44) (reply to #1) The information in /etc/X11/xdm/Keyboard.map can be used for a new start. #2: Jiří Suchomel (jsuchome) (2011-10-14 11:34:50) BTW, don't you know how other distros are doing it? Is there any common mapping from locale (de_DE) to console key map and X11 keyboard map? Actually, if we'd create some new file for it, I'd still more like to have it not inside YaST filesystem subtree, so it is easily available to potential other applications. #4: Stefan Dirsch (sndirsch) (2011-10-14 11:52:09) (reply to #2) I don't know how other distros handle this. You would like to figure it out? Please go ahead. I always thought YaST is our config tool. I would go for a config file/configuration, which is read by the usual desktops like KDE, Gnome, Xfce, etc to use this keyboard setting by default (global keyboard configuration) unless the user choses a different one. And that way finally get rid of this /etc/X11/xorg.conf. d/90-keytable.conf snippet created by /etc/X11/xdm/keytable. And yes, this will no longer cover the twm/fvwm2 user. #5: Jiří Suchomel (jsuchome) (2012-01-05 11:07:35) 1. So, YaST should offer all X11 layouts from start: where can I find the list of them? I assume there's a list, which is used buy KDE/GNOME tools. I think we should not use only the subset from /etc/X11/xdm/Keyboard.map. 2. YaST needs to determine which layout to used as defalt, based on user language during the installation. But this could stay YaST internal, as it is relevant to installation only. 3. Based on selected X11 layout, YaST should set also console keyboard. The mapping of X11-> console could be taken from current /etc/X11/xdm/Keyboard.map (it does not cover all X11 layouts, but that is fine) and could probably stay internal in YaST. Or do you think it makes sense to make it public for any other (desktop) applications? 4. The variable in KEYTABLE in /etc/sysconfig/keyboard could probably stay with current meaning. 5. We probably need to save X11 keyboard information saved somewhere (esp. during installation, when setxkbmap call is not available), and this info would be read by desktops to apply the layout, right? Seems like such config should contain all options needed for setxkbmap so other conversions are not needed. What do you think, could use /etc/sysconfig/keyboard for that? With the values like X11_LAYOUT, X11_VARIANT etc.? #6: Stefan Dirsch (sndirsch) (2012-01-05 12:28:04) (reply to #5) @1: I'm not sure whether KDE/GNOME tools use a static list for this or if they figure this out on-the-fly via libxkb and how. Please ask our KDE/GNOME developers. They should know better than me. @2: I agree. Default should depend on the language. Unless we can detect the keyboard language ... @3: I agree. I don't think desktop applications are interested in Linux console keyboard layout. :-) @4: Sure. I agree. This variable can stay with the current meaning. @5: Basically I agree, but I wouldn't split this into several options (of course YaST internal you do this). Just all options for the setxkbmap command in one string. #7: Jiří Suchomel (jsuchome) (2012-01-09 14:11:59) Tested Fedora 16: installer offers more layouts than we do, but I think not all of X11 available. Console keyboard does not seem to be configured. /etc/sysconfig/keyboard contains the keys KEYTABLE, MODEL, LAYOUT and VARIANT, which is close to our proposal. #8: Jiří Suchomel (jsuchome) (2012-01-09 14:40:57) Ubuntu installer seems to offer full X11 layouts support. After installation, console keyboard is probably set as well, but not console font, which results in unusable situation (tested CZ layout) #9: Jiří Suchomel (jsuchome) (2012-01-10 11:30:34) Jiri, what is your point of view? #10: Jiri Srain (jsrain) (2012-01-19 09:59:05) (reply to #9) I don't really see the value of this feature. I understand that there is a burden of maintaining a conversion table between console and X11 layouts, but I don't see the alternative (moving it between packages does not really help). How often are we asked to add another layout? + #11: Diggory Hardy (d_hardy) (2012-04-15 10:23:50) + To answer a question above, KDE/GNOME use /usr/share/X11/xkb/rules/base. + xml to find keyboards, layouts and variants. Jiri, maybe you're not + asked to add layouts very often (can you add Colemak please?), but it + makes using anything not listed a pain. I'm using a custom xkb layout + (no console equivalent) and can set it fine using setxkbmap but not on + X-server start. + To add a little perspective, debian has a file at /etc/default/keyboard + controlling the default X11 layout. I think they then do the opposite + to you and generate/find a console layout based on the xkb layout. + You'd have to ask someone else for the details. -- openSUSE Feature: https://features.opensuse.org/309487
Feature changed by: Stefan Dirsch (sndirsch) Feature #309487, revision 27 Title: Clean out X11 keyboard configuration in YaST openSUSE-11.4: Rejected by Stefan Dirsch (sndirsch) reject date: 2011-03-29 17:51:18 reject reason: Obviously not being addressed. Priority Requester: Important - openSUSE Distribution: Unconfirmed + openSUSE Distribution: Duplicate of #318355 + Master status: Unconfirmed Priority Requester: Desirable Requested by: Jiří Suchomel (jsuchome) Partner organization: openSUSE.org Description: Currently, 'yast2 keyboard' is using kind of strange way of determining which X11 keyboard layout to use. There's a map of internal YaST keyboard names, to which the list of kbd console maps is mapped (like, us.map.gz). Such console map is taken as a parameter for calling /usr/sbin/xkbctrl script, which returns the informations about corresponding X11 keyboard layout (usable for setxkbmap). One problem is that not for all languages, there's a sense to have console map, and because of this situation in YaST, we are using files like ar.map.gz, which are only links to us.map.gz. Other part is that the list of X11 keyboard layouts is part of sax2- tools package which we probably want to drop. New solution would mean that YaST has all the information currently provided by xkbctrl: either by building its own data structure (if there's no other application using it), or using a better way to get the data YaST needs to know. References: https://bugzilla.novell.com/show_bug.cgi?id=603950 https://bugzilla.novell.com/show_bug.cgi?id=601587 https://bugzilla.novell.com/show_bug.cgi?id=725468 + Relations: + - (feature/duplicate: 318355) Discussion: #1: Jiří Suchomel (jsuchome) (2011-10-13 15:24:42) Stefan, where does YaST get the info about which setxkbmap command to call? #3: Stefan Dirsch (sndirsch) (2011-10-14 11:41:44) (reply to #1) The information in /etc/X11/xdm/Keyboard.map can be used for a new start. #2: Jiří Suchomel (jsuchome) (2011-10-14 11:34:50) BTW, don't you know how other distros are doing it? Is there any common mapping from locale (de_DE) to console key map and X11 keyboard map? Actually, if we'd create some new file for it, I'd still more like to have it not inside YaST filesystem subtree, so it is easily available to potential other applications. #4: Stefan Dirsch (sndirsch) (2011-10-14 11:52:09) (reply to #2) I don't know how other distros handle this. You would like to figure it out? Please go ahead. I always thought YaST is our config tool. I would go for a config file/configuration, which is read by the usual desktops like KDE, Gnome, Xfce, etc to use this keyboard setting by default (global keyboard configuration) unless the user choses a different one. And that way finally get rid of this /etc/X11/xorg.conf. d/90-keytable.conf snippet created by /etc/X11/xdm/keytable. And yes, this will no longer cover the twm/fvwm2 user. #5: Jiří Suchomel (jsuchome) (2012-01-05 11:07:35) 1. So, YaST should offer all X11 layouts from start: where can I find the list of them? I assume there's a list, which is used buy KDE/GNOME tools. I think we should not use only the subset from /etc/X11/xdm/Keyboard.map. 2. YaST needs to determine which layout to used as defalt, based on user language during the installation. But this could stay YaST internal, as it is relevant to installation only. 3. Based on selected X11 layout, YaST should set also console keyboard. The mapping of X11-> console could be taken from current /etc/X11/xdm/Keyboard.map (it does not cover all X11 layouts, but that is fine) and could probably stay internal in YaST. Or do you think it makes sense to make it public for any other (desktop) applications? 4. The variable in KEYTABLE in /etc/sysconfig/keyboard could probably stay with current meaning. 5. We probably need to save X11 keyboard information saved somewhere (esp. during installation, when setxkbmap call is not available), and this info would be read by desktops to apply the layout, right? Seems like such config should contain all options needed for setxkbmap so other conversions are not needed. What do you think, could use /etc/sysconfig/keyboard for that? With the values like X11_LAYOUT, X11_VARIANT etc.? #6: Stefan Dirsch (sndirsch) (2012-01-05 12:28:04) (reply to #5) @1: I'm not sure whether KDE/GNOME tools use a static list for this or if they figure this out on-the-fly via libxkb and how. Please ask our KDE/GNOME developers. They should know better than me. @2: I agree. Default should depend on the language. Unless we can detect the keyboard language ... @3: I agree. I don't think desktop applications are interested in Linux console keyboard layout. :-) @4: Sure. I agree. This variable can stay with the current meaning. @5: Basically I agree, but I wouldn't split this into several options (of course YaST internal you do this). Just all options for the setxkbmap command in one string. #7: Jiří Suchomel (jsuchome) (2012-01-09 14:11:59) Tested Fedora 16: installer offers more layouts than we do, but I think not all of X11 available. Console keyboard does not seem to be configured. /etc/sysconfig/keyboard contains the keys KEYTABLE, MODEL, LAYOUT and VARIANT, which is close to our proposal. #8: Jiří Suchomel (jsuchome) (2012-01-09 14:40:57) Ubuntu installer seems to offer full X11 layouts support. After installation, console keyboard is probably set as well, but not console font, which results in unusable situation (tested CZ layout) #9: Jiří Suchomel (jsuchome) (2012-01-10 11:30:34) Jiri, what is your point of view? #10: Jiri Srain (jsrain) (2012-01-19 09:59:05) (reply to #9) I don't really see the value of this feature. I understand that there is a burden of maintaining a conversion table between console and X11 layouts, but I don't see the alternative (moving it between packages does not really help). How often are we asked to add another layout? #11: Diggory Hardy (d_hardy) (2012-04-15 10:23:50) To answer a question above, KDE/GNOME use /usr/share/X11/xkb/rules/base. xml to find keyboards, layouts and variants. Jiri, maybe you're not asked to add layouts very often (can you add Colemak please?), but it makes using anything not listed a pain. I'm using a custom xkb layout (no console equivalent) and can set it fine using setxkbmap but not on X-server start. To add a little perspective, debian has a file at /etc/default/keyboard controlling the default X11 layout. I think they then do the opposite to you and generate/find a console layout based on the xkb layout. You'd have to ask someone else for the details. + #15: Stefan Dirsch (sndirsch) (2015-06-19 10:55:59) + Should be addressed together with FATE#318355 (duplicate). -- openSUSE Feature: https://features.opensuse.org/309487
Feature changed by: Mindaugas Baranauskas (embar-) Feature #309487, revision 28 Title: Clean out X11 keyboard configuration in YaST openSUSE-11.4: Rejected by Stefan Dirsch (sndirsch) reject date: 2011-03-29 17:51:18 reject reason: Obviously not being addressed. Priority Requester: Important openSUSE Distribution: Duplicate of #318355 - Master status: Unconfirmed + Master status: Done Priority Requester: Desirable Requested by: Jiří Suchomel (jsuchome) Partner organization: openSUSE.org Description: Currently, 'yast2 keyboard' is using kind of strange way of determining which X11 keyboard layout to use. There's a map of internal YaST keyboard names, to which the list of kbd console maps is mapped (like, us.map.gz). Such console map is taken as a parameter for calling /usr/sbin/xkbctrl script, which returns the informations about corresponding X11 keyboard layout (usable for setxkbmap). One problem is that not for all languages, there's a sense to have console map, and because of this situation in YaST, we are using files like ar.map.gz, which are only links to us.map.gz. Other part is that the list of X11 keyboard layouts is part of sax2- tools package which we probably want to drop. New solution would mean that YaST has all the information currently provided by xkbctrl: either by building its own data structure (if there's no other application using it), or using a better way to get the data YaST needs to know. References: https://bugzilla.novell.com/show_bug.cgi?id=603950 https://bugzilla.novell.com/show_bug.cgi?id=601587 https://bugzilla.novell.com/show_bug.cgi?id=725468 Relations: - (feature/duplicate: 318355) Discussion: #1: Jiří Suchomel (jsuchome) (2011-10-13 15:24:42) Stefan, where does YaST get the info about which setxkbmap command to call? #3: Stefan Dirsch (sndirsch) (2011-10-14 11:41:44) (reply to #1) The information in /etc/X11/xdm/Keyboard.map can be used for a new start. #2: Jiří Suchomel (jsuchome) (2011-10-14 11:34:50) BTW, don't you know how other distros are doing it? Is there any common mapping from locale (de_DE) to console key map and X11 keyboard map? Actually, if we'd create some new file for it, I'd still more like to have it not inside YaST filesystem subtree, so it is easily available to potential other applications. #4: Stefan Dirsch (sndirsch) (2011-10-14 11:52:09) (reply to #2) I don't know how other distros handle this. You would like to figure it out? Please go ahead. I always thought YaST is our config tool. I would go for a config file/configuration, which is read by the usual desktops like KDE, Gnome, Xfce, etc to use this keyboard setting by default (global keyboard configuration) unless the user choses a different one. And that way finally get rid of this /etc/X11/xorg.conf. d/90-keytable.conf snippet created by /etc/X11/xdm/keytable. And yes, this will no longer cover the twm/fvwm2 user. #5: Jiří Suchomel (jsuchome) (2012-01-05 11:07:35) 1. So, YaST should offer all X11 layouts from start: where can I find the list of them? I assume there's a list, which is used buy KDE/GNOME tools. I think we should not use only the subset from /etc/X11/xdm/Keyboard.map. 2. YaST needs to determine which layout to used as defalt, based on user language during the installation. But this could stay YaST internal, as it is relevant to installation only. 3. Based on selected X11 layout, YaST should set also console keyboard. The mapping of X11-> console could be taken from current /etc/X11/xdm/Keyboard.map (it does not cover all X11 layouts, but that is fine) and could probably stay internal in YaST. Or do you think it makes sense to make it public for any other (desktop) applications? 4. The variable in KEYTABLE in /etc/sysconfig/keyboard could probably stay with current meaning. 5. We probably need to save X11 keyboard information saved somewhere (esp. during installation, when setxkbmap call is not available), and this info would be read by desktops to apply the layout, right? Seems like such config should contain all options needed for setxkbmap so other conversions are not needed. What do you think, could use /etc/sysconfig/keyboard for that? With the values like X11_LAYOUT, X11_VARIANT etc.? #6: Stefan Dirsch (sndirsch) (2012-01-05 12:28:04) (reply to #5) @1: I'm not sure whether KDE/GNOME tools use a static list for this or if they figure this out on-the-fly via libxkb and how. Please ask our KDE/GNOME developers. They should know better than me. @2: I agree. Default should depend on the language. Unless we can detect the keyboard language ... @3: I agree. I don't think desktop applications are interested in Linux console keyboard layout. :-) @4: Sure. I agree. This variable can stay with the current meaning. @5: Basically I agree, but I wouldn't split this into several options (of course YaST internal you do this). Just all options for the setxkbmap command in one string. #7: Jiří Suchomel (jsuchome) (2012-01-09 14:11:59) Tested Fedora 16: installer offers more layouts than we do, but I think not all of X11 available. Console keyboard does not seem to be configured. /etc/sysconfig/keyboard contains the keys KEYTABLE, MODEL, LAYOUT and VARIANT, which is close to our proposal. #8: Jiří Suchomel (jsuchome) (2012-01-09 14:40:57) Ubuntu installer seems to offer full X11 layouts support. After installation, console keyboard is probably set as well, but not console font, which results in unusable situation (tested CZ layout) #9: Jiří Suchomel (jsuchome) (2012-01-10 11:30:34) Jiri, what is your point of view? #10: Jiri Srain (jsrain) (2012-01-19 09:59:05) (reply to #9) I don't really see the value of this feature. I understand that there is a burden of maintaining a conversion table between console and X11 layouts, but I don't see the alternative (moving it between packages does not really help). How often are we asked to add another layout? #11: Diggory Hardy (d_hardy) (2012-04-15 10:23:50) To answer a question above, KDE/GNOME use /usr/share/X11/xkb/rules/base. xml to find keyboards, layouts and variants. Jiri, maybe you're not asked to add layouts very often (can you add Colemak please?), but it makes using anything not listed a pain. I'm using a custom xkb layout (no console equivalent) and can set it fine using setxkbmap but not on X-server start. To add a little perspective, debian has a file at /etc/default/keyboard controlling the default X11 layout. I think they then do the opposite to you and generate/find a console layout based on the xkb layout. You'd have to ask someone else for the details. #15: Stefan Dirsch (sndirsch) (2015-06-19 10:55:59) Should be addressed together with FATE#318355 (duplicate). -- openSUSE Feature: https://features.opensuse.org/309487
participants (1)
-
fate_noreply＠suse.de