Bug#306334: kbd-chooser: Distinguish between "no keyboard" and "skip config"
> Actually "no keyboard" is more like "keep default kernel keymap", i.e.
> "Do not configure keyboard".
> Sparc issues have shown that not selecting a keymap can be a very useful
> The patch makes the difference between the two situations more clear and
> _always_ adds the "Do not configure keyboard" option (normally only shown
> at medium/low prio) for non-sercon/UML installs.
> The default value for "kbd architecture" does not change from the current
> kbd-chooser/no-keyboard: No keyboard to configure
> kbd-chooser/skip-config: Do not configure keyboard
> These templates are fairly close. In principle one could be dropped for
> space considerations. My preference would be to keep the second in that case.
I'm not sure I understand well. Are there situations where these two
options may be shown (you know I'm not good at reading code..:-))) ?
If so, the puzzling task is making the two different enough for not
If they're not meant to be shown together, then we either need to have
them share the same wording....or add a translator comment to explain