Change in the wiki, by Samuel: > * Include kbd-udeb to the initrd images > - * (to be detailed) get rid of console-data (From Anton: "The most difficult part inside console-setup is to make the model/layout strings translatable. The X upstream provides translations in a xml file but I have no idea how to use them.) > + * (to be detailed) get rid of console-data (From Anton: "The most difficult part inside console-setup is to make the model/layout strings translatable. The X upstream provides translations in a xml file but I have no idea how to use them. ST: translations are not in the xml file, they are in mere .po files in po/ of xkeyboard-config (or .mo in the .deb), ideally we could just give their path to po2debconf) > + * parse base.xml to generate locale/country -> layout/variant default choice (ask ST, some bugs are being fixed in xkeyboard-config). > + * parse base.xml to get e.g; compose:caps) default_compose='Caps Lock';; (ask ST) (translations are also available in the po/ directory of xkeyboard-config) > * (optional?) use the Ubuntu way to set the keymap? If I understand well, the strings used by console-setup for keymap names are indeed used from an XML file...that's built by xkeyboard-config, where these strings are translatable through PO files. If that's right, it means that a main blocker for the swith to console-setup does not really exist and we could re-consider this more carefully. Am I right? (Samuel, CC'ing you to get attention, only. I know you're subscribed to -boot)
Attachment:
signature.asc
Description: Digital signature