[openFATE 305846] Add the us_int (us international with euro sign keyboard)
Feature added by: Joop Boonen (worldcitizen) Feature #305846, revision 1, last change by Title: Add the us_int (us international with euro sign keyboard) openSUSE-11.2: Unconfirmed Priority Requester: Important openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Joop Boonen (worldcitizen) Description: Add the us_int (us international with euro sign on "5" key keyboard) in the choices in the installation process (when the keyboard can be chosen). This way it'll be easier to choose this lay-out. -- openSUSE Feature: https://features.opensuse.org/305846
Feature changed by: Stephan Kulow (coolo) Feature #305846, revision 4 Title: Add the us_int (us international with euro sign keyboard) - openSUSE-11.2: Unconfirmed + openSUSE-11.2: Evaluation Priority Requester: Important + Projectmanager: Neutral - openSUSE-11.3: Unconfirmed - Priority - Requester: Important Requested by: Joop Boonen (worldcitizen) Description: Add the us_int (us international with euro sign on "5" key keyboard) in the choices in the installation process (when the keyboard can be chosen). This way it'll be easier to choose this lay-out. + Discussion: + #1: Stephan Kulow (coolo) (2009-03-30 20:15:00) + such small missing features are really better in bugzilla. Now 5 or + more people have to look at it. -- openSUSE Feature: https://features.opensuse.org/305846
Feature changed by: Jiri Srain (jsrain) Feature #305846, revision 5 Title: Add the us_int (us international with euro sign keyboard) - openSUSE-11.2: Evaluation + openSUSE-11.2: Candidate Priority Requester: Important Projectmanager: Neutral Requested by: Joop Boonen (worldcitizen) Description: Add the us_int (us international with euro sign on "5" key keyboard) in the choices in the installation process (when the keyboard can be chosen). This way it'll be easier to choose this lay-out. Discussion: #1: Stephan Kulow (coolo) (2009-03-30 20:15:00) such small missing features are really better in bugzilla. Now 5 or more people have to look at it. -- openSUSE Feature: https://features.opensuse.org/305846
Feature changed by: Jiří Suchomel (jsuchome) Feature #305846, revision 6 Title: Add the us_int (us international with euro sign keyboard) openSUSE-11.2: Candidate Priority Requester: Important Projectmanager: Neutral Requested by: Joop Boonen (worldcitizen) Description: Add the us_int (us international with euro sign on "5" key keyboard) in the choices in the installation process (when the keyboard can be chosen). This way it'll be easier to choose this lay-out. Discussion: #1: Stephan Kulow (coolo) (2009-03-30 20:15:00) such small missing features are really better in bugzilla. Now 5 or more people have to look at it. + #2: Jiří Suchomel (jsuchome) (2009-04-23 11:51:50) + What's the console map file for this layout? Do we have one? -- openSUSE Feature: https://features.opensuse.org/305846
Feature changed by: Michal Marek (michal-m) Feature #305846, revision 12 Title: Add the us_int (us international with euro sign keyboard) openSUSE-11.2: Candidate Priority Requester: Important Projectmanager: Neutral Requested by: Joop Boonen (worldcitizen) Description: Add the us_int (us international with euro sign on "5" key keyboard) in the choices in the installation process (when the keyboard can be chosen). This way it'll be easier to choose this lay-out. Discussion: #1: Stephan Kulow (coolo) (2009-03-30 20:15:00) such small missing features are really better in bugzilla. Now 5 or more people have to look at it. #2: Jiří Suchomel (jsuchome) (2009-04-23 11:51:50) What's the console map file for this layout? Do we have one? #3: Michal Marek (michal-m) (2009-04-30 16:16:15) (reply to #2) The 'us' console keymap includes the 'euro1' keymap which has the euro sign under Altgr+5. I think there doesn't need to be done anything for the console. #4: Jiří Suchomel (jsuchome) (2009-05-04 08:58:44) (reply to #3) I see, but for YaST, this is not such a good news. YaST Keyboard has a list of keyboard layouts, indexed by console map files. For setting X11 layout, it uses the mapping from console map to X11 layout saved in /usr/share/sax/sysp/maps/Keyboard.map. That's why I need some uniquie key which would be correctly mapped to X11 config. I see 2 solutions here: 1. create a console map file with unique name (us_int?), that would be just a link to us.map.gz (just like khmer.map.gz or korean.map.gz). Than I need a new entry in /usr/share/sax/sysp/maps/Keyboard.map that would map this new key to correct X11 setting. 2. Or I could enhance YaST Keyboard module to not relay on console map as a index key. But that way, I'd need a full list of parameters for setxkbmap (equivalent to an entry in /usr/share/sax/sysp/maps/Keyboard. map file) which I could save somewhere and call when necessary. Michal, Stefan, what do you think? + #7: Michal Marek (michal-m) (2009-05-13 09:57:54) (reply to #4) + Not really related to whether this feature is going to be accepted or + not, but: + Nowadays, most people don't really care about console keymaps, this + request is also primarily about the X11 keyboard layout I guess. While + it's not a big issue to add some symlink to the kbd package from time + to time, it might be a good idea to stop using the console map name as + a primary index and use some fabricated id instead, e.g. + #ID CONSOLE MODEL LAYOUT ... + us : us : microsoftpro : us ... + us_int : us : microsoftpro : us_int ... + IMO the current map looks like "which setxkbmap options mimick given + console map the best", while nowadays it would be more logical to ask + "which consolemap roughly matches given setxkbmap config". Also, there + is a number of console maps that map to the same X11 layout (e.g. the + five br-* ones), does yast really need to offer all these variants if + the result is the same (in X)? -- openSUSE Feature: https://features.opensuse.org/305846
Feature changed by: Jiří Suchomel (jsuchome) Feature #305846, revision 13 Title: Add the us_int (us international with euro sign keyboard) openSUSE-11.2: Candidate Priority Requester: Important Projectmanager: Neutral Requested by: Joop Boonen (worldcitizen) Description: Add the us_int (us international with euro sign on "5" key keyboard) in the choices in the installation process (when the keyboard can be chosen). This way it'll be easier to choose this lay-out. Discussion: #1: Stephan Kulow (coolo) (2009-03-30 20:15:00) such small missing features are really better in bugzilla. Now 5 or more people have to look at it. #2: Jiří Suchomel (jsuchome) (2009-04-23 11:51:50) What's the console map file for this layout? Do we have one? #3: Michal Marek (michal-m) (2009-04-30 16:16:15) (reply to #2) The 'us' console keymap includes the 'euro1' keymap which has the euro sign under Altgr+5. I think there doesn't need to be done anything for the console. #4: Jiří Suchomel (jsuchome) (2009-05-04 08:58:44) (reply to #3) I see, but for YaST, this is not such a good news. YaST Keyboard has a list of keyboard layouts, indexed by console map files. For setting X11 layout, it uses the mapping from console map to X11 layout saved in /usr/share/sax/sysp/maps/Keyboard.map. That's why I need some uniquie key which would be correctly mapped to X11 config. I see 2 solutions here: 1. create a console map file with unique name (us_int?), that would be just a link to us.map.gz (just like khmer.map.gz or korean.map.gz). Than I need a new entry in /usr/share/sax/sysp/maps/Keyboard.map that would map this new key to correct X11 setting. 2. Or I could enhance YaST Keyboard module to not relay on console map as a index key. But that way, I'd need a full list of parameters for setxkbmap (equivalent to an entry in /usr/share/sax/sysp/maps/Keyboard. map file) which I could save somewhere and call when necessary. Michal, Stefan, what do you think? #7: Michal Marek (michal-m) (2009-05-13 09:57:54) (reply to #4) Not really related to whether this feature is going to be accepted or not, but: Nowadays, most people don't really care about console keymaps, this request is also primarily about the X11 keyboard layout I guess. While it's not a big issue to add some symlink to the kbd package from time to time, it might be a good idea to stop using the console map name as a primary index and use some fabricated id instead, e.g. #ID CONSOLE MODEL LAYOUT ... us : us : microsoftpro : us ... us_int : us : microsoftpro : us_int ... IMO the current map looks like "which setxkbmap options mimick given console map the best", while nowadays it would be more logical to ask "which consolemap roughly matches given setxkbmap config". Also, there is a number of console maps that map to the same X11 layout (e.g. the five br-* ones), does yast really need to offer all these variants if the result is the same (in X)? + #8: Jiří Suchomel (jsuchome) (2009-05-13 10:08:12) (reply to #7) + I agree that using a console map as an index in YaST maps does not make + much sense and we should go forward to using X11 layout names directly + (if time permits...) + However, note that this is hidden to user and until this time, we + haven't serious problems with current approach. -- openSUSE Feature: https://features.opensuse.org/305846
Feature changed by: Stefan Dirsch (sndirsch) Feature #305846, revision 14 Title: Add the us_int (us international with euro sign keyboard) openSUSE-11.2: Candidate Priority Requester: Important Projectmanager: Neutral Requested by: Joop Boonen (worldcitizen) Description: Add the us_int (us international with euro sign on "5" key keyboard) in the choices in the installation process (when the keyboard can be chosen). This way it'll be easier to choose this lay-out. Discussion: #1: Stephan Kulow (coolo) (2009-03-30 20:15:00) such small missing features are really better in bugzilla. Now 5 or more people have to look at it. #2: Jiří Suchomel (jsuchome) (2009-04-23 11:51:50) What's the console map file for this layout? Do we have one? #3: Michal Marek (michal-m) (2009-04-30 16:16:15) (reply to #2) The 'us' console keymap includes the 'euro1' keymap which has the euro sign under Altgr+5. I think there doesn't need to be done anything for the console. #4: Jiří Suchomel (jsuchome) (2009-05-04 08:58:44) (reply to #3) I see, but for YaST, this is not such a good news. YaST Keyboard has a list of keyboard layouts, indexed by console map files. For setting X11 layout, it uses the mapping from console map to X11 layout saved in /usr/share/sax/sysp/maps/Keyboard.map. That's why I need some uniquie key which would be correctly mapped to X11 config. I see 2 solutions here: 1. create a console map file with unique name (us_int?), that would be just a link to us.map.gz (just like khmer.map.gz or korean.map.gz). Than I need a new entry in /usr/share/sax/sysp/maps/Keyboard.map that would map this new key to correct X11 setting. 2. Or I could enhance YaST Keyboard module to not relay on console map as a index key. But that way, I'd need a full list of parameters for setxkbmap (equivalent to an entry in /usr/share/sax/sysp/maps/Keyboard. map file) which I could save somewhere and call when necessary. Michal, Stefan, what do you think? #7: Michal Marek (michal-m) (2009-05-13 09:57:54) (reply to #4) Not really related to whether this feature is going to be accepted or not, but: Nowadays, most people don't really care about console keymaps, this request is also primarily about the X11 keyboard layout I guess. While it's not a big issue to add some symlink to the kbd package from time to time, it might be a good idea to stop using the console map name as a primary index and use some fabricated id instead, e.g. #ID CONSOLE MODEL LAYOUT ... us : us : microsoftpro : us ... us_int : us : microsoftpro : us_int ... IMO the current map looks like "which setxkbmap options mimick given console map the best", while nowadays it would be more logical to ask "which consolemap roughly matches given setxkbmap config". Also, there is a number of console maps that map to the same X11 layout (e.g. the five br-* ones), does yast really need to offer all these variants if the result is the same (in X)? #8: Jiří Suchomel (jsuchome) (2009-05-13 10:08:12) (reply to #7) I agree that using a console map as an index in YaST maps does not make much sense and we should go forward to using X11 layout names directly (if time permits...) However, note that this is hidden to user and until this time, we haven't serious problems with current approach. + #9: Stefan Dirsch (sndirsch) (2009-05-13 10:40:23) (reply to #7) + What you're requesting is to replace YaST's keyboard configuration with + the SaX2 keyboard configuration, which we want to get rid of since we + want to switch to dynamic X configuration in general. Users should + configure their keyboard via the desktop tool. A basic keyboard layout + for global configuration should be enough. We have this already (in + 11.2, which no longer uses a configuration in xorg.conf, + via/etc/X11/xdm/keytable4hal) . -- openSUSE Feature: https://features.opensuse.org/305846
Feature changed by: Michal Marek (michal-m) Feature #305846, revision 15 Title: Add the us_int (us international with euro sign keyboard) openSUSE-11.2: Candidate Priority Requester: Important Projectmanager: Neutral Requested by: Joop Boonen (worldcitizen) Description: Add the us_int (us international with euro sign on "5" key keyboard) in the choices in the installation process (when the keyboard can be chosen). This way it'll be easier to choose this lay-out. Discussion: #1: Stephan Kulow (coolo) (2009-03-30 20:15:00) such small missing features are really better in bugzilla. Now 5 or more people have to look at it. #2: Jiří Suchomel (jsuchome) (2009-04-23 11:51:50) What's the console map file for this layout? Do we have one? #3: Michal Marek (michal-m) (2009-04-30 16:16:15) (reply to #2) The 'us' console keymap includes the 'euro1' keymap which has the euro sign under Altgr+5. I think there doesn't need to be done anything for the console. #4: Jiří Suchomel (jsuchome) (2009-05-04 08:58:44) (reply to #3) I see, but for YaST, this is not such a good news. YaST Keyboard has a list of keyboard layouts, indexed by console map files. For setting X11 layout, it uses the mapping from console map to X11 layout saved in /usr/share/sax/sysp/maps/Keyboard.map. That's why I need some uniquie key which would be correctly mapped to X11 config. I see 2 solutions here: 1. create a console map file with unique name (us_int?), that would be just a link to us.map.gz (just like khmer.map.gz or korean.map.gz). Than I need a new entry in /usr/share/sax/sysp/maps/Keyboard.map that would map this new key to correct X11 setting. 2. Or I could enhance YaST Keyboard module to not relay on console map as a index key. But that way, I'd need a full list of parameters for setxkbmap (equivalent to an entry in /usr/share/sax/sysp/maps/Keyboard. map file) which I could save somewhere and call when necessary. Michal, Stefan, what do you think? #7: Michal Marek (michal-m) (2009-05-13 09:57:54) (reply to #4) Not really related to whether this feature is going to be accepted or not, but: Nowadays, most people don't really care about console keymaps, this request is also primarily about the X11 keyboard layout I guess. While it's not a big issue to add some symlink to the kbd package from time to time, it might be a good idea to stop using the console map name as a primary index and use some fabricated id instead, e.g. #ID CONSOLE MODEL LAYOUT ... us : us : microsoftpro : us ... us_int : us : microsoftpro : us_int ... IMO the current map looks like "which setxkbmap options mimick given console map the best", while nowadays it would be more logical to ask "which consolemap roughly matches given setxkbmap config". Also, there is a number of console maps that map to the same X11 layout (e.g. the five br-* ones), does yast really need to offer all these variants if the result is the same (in X)? #8: Jiří Suchomel (jsuchome) (2009-05-13 10:08:12) (reply to #7) I agree that using a console map as an index in YaST maps does not make much sense and we should go forward to using X11 layout names directly (if time permits...) However, note that this is hidden to user and until this time, we haven't serious problems with current approach. #9: Stefan Dirsch (sndirsch) (2009-05-13 10:40:23) (reply to #7) What you're requesting is to replace YaST's keyboard configuration with the SaX2 keyboard configuration, which we want to get rid of since we want to switch to dynamic X configuration in general. Users should configure their keyboard via the desktop tool. A basic keyboard layout for global configuration should be enough. We have this already (in 11.2, which no longer uses a configuration in xorg.conf, via/etc/X11/xdm/keytable4hal) . + #10: Michal Marek (michal-m) (2009-05-13 11:15:37) (reply to #9) + I'm not _requesting_ anything :-) and I also don't know the details of + how sax and yast configure the keyboard. It just looked strange to me + to derive the X11 layout from the console layout name, but if this is + not visible to the user and if it is only needed to get a basic layout, + there is probably no problem and sorry for the noise. -- openSUSE Feature: https://features.opensuse.org/305846
Feature changed by: Jiří Suchomel (jsuchome) Feature #305846, revision 18 Title: Add the us_int (us international with euro sign keyboard) - openSUSE-11.2: Candidate + openSUSE-11.2: Evaluation Priority Requester: Important Projectmanager: Neutral Requested by: Joop Boonen (worldcitizen) Description: Add the us_int (us international with euro sign on "5" key keyboard) in the choices in the installation process (when the keyboard can be chosen). This way it'll be easier to choose this lay-out. Discussion: #1: Stephan Kulow (coolo) (2009-03-30 20:15:00) such small missing features are really better in bugzilla. Now 5 or more people have to look at it. #2: Jiří Suchomel (jsuchome) (2009-04-23 11:51:50) What's the console map file for this layout? Do we have one? #3: Michal Marek (michal-m) (2009-04-30 16:16:15) (reply to #2) The 'us' console keymap includes the 'euro1' keymap which has the euro sign under Altgr+5. I think there doesn't need to be done anything for the console. #4: Jiří Suchomel (jsuchome) (2009-05-04 08:58:44) (reply to #3) I see, but for YaST, this is not such a good news. YaST Keyboard has a list of keyboard layouts, indexed by console map files. For setting X11 layout, it uses the mapping from console map to X11 layout saved in /usr/share/sax/sysp/maps/Keyboard.map. That's why I need some uniquie key which would be correctly mapped to X11 config. I see 2 solutions here: 1. create a console map file with unique name (us_int?), that would be just a link to us.map.gz (just like khmer.map.gz or korean.map.gz). Than I need a new entry in /usr/share/sax/sysp/maps/Keyboard.map that would map this new key to correct X11 setting. 2. Or I could enhance YaST Keyboard module to not relay on console map as a index key. But that way, I'd need a full list of parameters for setxkbmap (equivalent to an entry in /usr/share/sax/sysp/maps/Keyboard. map file) which I could save somewhere and call when necessary. Michal, Stefan, what do you think? #7: Michal Marek (michal-m) (2009-05-13 09:57:54) (reply to #4) Not really related to whether this feature is going to be accepted or not, but: Nowadays, most people don't really care about console keymaps, this request is also primarily about the X11 keyboard layout I guess. While it's not a big issue to add some symlink to the kbd package from time to time, it might be a good idea to stop using the console map name as a primary index and use some fabricated id instead, e.g. #ID CONSOLE MODEL LAYOUT ... us : us : microsoftpro : us ... us_int : us : microsoftpro : us_int ... IMO the current map looks like "which setxkbmap options mimick given console map the best", while nowadays it would be more logical to ask "which consolemap roughly matches given setxkbmap config". Also, there is a number of console maps that map to the same X11 layout (e.g. the five br-* ones), does yast really need to offer all these variants if the result is the same (in X)? #8: Jiří Suchomel (jsuchome) (2009-05-13 10:08:12) (reply to #7) I agree that using a console map as an index in YaST maps does not make much sense and we should go forward to using X11 layout names directly (if time permits...) However, note that this is hidden to user and until this time, we haven't serious problems with current approach. #9: Stefan Dirsch (sndirsch) (2009-05-13 10:40:23) (reply to #7) What you're requesting is to replace YaST's keyboard configuration with the SaX2 keyboard configuration, which we want to get rid of since we want to switch to dynamic X configuration in general. Users should configure their keyboard via the desktop tool. A basic keyboard layout for global configuration should be enough. We have this already (in 11.2, which no longer uses a configuration in xorg.conf, via/etc/X11/xdm/keytable4hal) . #10: Michal Marek (michal-m) (2009-05-13 11:15:37) (reply to #9) I'm not _requesting_ anything :-) and I also don't know the details of how sax and yast configure the keyboard. It just looked strange to me to derive the X11 layout from the console layout name, but if this is not visible to the user and if it is only needed to get a basic layout, there is probably no problem and sorry for the noise. -- openSUSE Feature: https://features.opensuse.org/305846
Feature changed by: Stephan Kulow (coolo) Feature #305846, revision 22 Title: Add the us_int (us international with euro sign keyboard) - openSUSE-11.2: Evaluation + openSUSE-11.2: Rejected by Stephan Kulow (coolo) + reject date: 2009-06-09 10:52:19 + reject reason: the support for killing the feature is bigger than the + support to do it. Priority Requester: Important Projectmanager: Neutral Requested by: Joop Boonen (worldcitizen) Description: Add the us_int (us international with euro sign on "5" key keyboard) in the choices in the installation process (when the keyboard can be chosen). This way it'll be easier to choose this lay-out. Discussion: #1: Stephan Kulow (coolo) (2009-03-30 20:15:00) such small missing features are really better in bugzilla. Now 5 or more people have to look at it. #2: Jiří Suchomel (jsuchome) (2009-04-23 11:51:50) What's the console map file for this layout? Do we have one? #3: Michal Marek (michal-m) (2009-04-30 16:16:15) (reply to #2) The 'us' console keymap includes the 'euro1' keymap which has the euro sign under Altgr+5. I think there doesn't need to be done anything for the console. #4: Jiří Suchomel (jsuchome) (2009-05-04 08:58:44) (reply to #3) I see, but for YaST, this is not such a good news. YaST Keyboard has a list of keyboard layouts, indexed by console map files. For setting X11 layout, it uses the mapping from console map to X11 layout saved in /usr/share/sax/sysp/maps/Keyboard.map. That's why I need some uniquie key which would be correctly mapped to X11 config. I see 2 solutions here: 1. create a console map file with unique name (us_int?), that would be just a link to us.map.gz (just like khmer.map.gz or korean.map.gz). Than I need a new entry in /usr/share/sax/sysp/maps/Keyboard.map that would map this new key to correct X11 setting. 2. Or I could enhance YaST Keyboard module to not relay on console map as a index key. But that way, I'd need a full list of parameters for setxkbmap (equivalent to an entry in /usr/share/sax/sysp/maps/Keyboard. map file) which I could save somewhere and call when necessary. Michal, Stefan, what do you think? #7: Michal Marek (michal-m) (2009-05-13 09:57:54) (reply to #4) Not really related to whether this feature is going to be accepted or not, but: Nowadays, most people don't really care about console keymaps, this request is also primarily about the X11 keyboard layout I guess. While it's not a big issue to add some symlink to the kbd package from time to time, it might be a good idea to stop using the console map name as a primary index and use some fabricated id instead, e.g. #ID CONSOLE MODEL LAYOUT ... us : us : microsoftpro : us ... us_int : us : microsoftpro : us_int ... IMO the current map looks like "which setxkbmap options mimick given console map the best", while nowadays it would be more logical to ask "which consolemap roughly matches given setxkbmap config". Also, there is a number of console maps that map to the same X11 layout (e.g. the five br-* ones), does yast really need to offer all these variants if the result is the same (in X)? #8: Jiří Suchomel (jsuchome) (2009-05-13 10:08:12) (reply to #7) I agree that using a console map as an index in YaST maps does not make much sense and we should go forward to using X11 layout names directly (if time permits...) However, note that this is hidden to user and until this time, we haven't serious problems with current approach. #9: Stefan Dirsch (sndirsch) (2009-05-13 10:40:23) (reply to #7) What you're requesting is to replace YaST's keyboard configuration with the SaX2 keyboard configuration, which we want to get rid of since we want to switch to dynamic X configuration in general. Users should configure their keyboard via the desktop tool. A basic keyboard layout for global configuration should be enough. We have this already (in 11.2, which no longer uses a configuration in xorg.conf, via/etc/X11/xdm/keytable4hal) . #10: Michal Marek (michal-m) (2009-05-13 11:15:37) (reply to #9) I'm not _requesting_ anything :-) and I also don't know the details of how sax and yast configure the keyboard. It just looked strange to me to derive the X11 layout from the console layout name, but if this is not visible to the user and if it is only needed to get a basic layout, there is probably no problem and sorry for the noise. -- openSUSE Feature: https://features.opensuse.org/305846
participants (1)
-
fate_noreply＠suse.de