On Wed, Nov 09, 2005 at 06:46:07AM +0100, Christian Perrier <[EMAIL PROTECTED]> was heard to say: > (please keep the CC list in answers. No need to CC me in private) > > > > > These are the shortcut keys you need to press when answering a Yes/No > > question. While the aptitude developers care i18n enough to give the > > possibility to localize this shortcut key, without a comment translators > > won't know they are supposed to translate them to a single key that > > stands for yes/no (in English, they'll be "y" and "n"). These shortcut > > keys are used quite often, for example, in the dialog of quitting > > aptitude. > > > What I'm wondering here is why doesn't aptitude use the locales > mechanisms for Y/N answers. > > As far as I know, locales include a part which describes "yes > expression" and "no expression" as "yesexpr" and "noexpr" in > LC_MESSAGES. > > For French locales, this is actually: > > LC_MESSAGES > yesexpr "^[oOyY].*" > noexpr "^[nN].*" > END LC_MESSAGES > > (the word for "yes" is "oui" and the word for "no" is "non"). This > means that any *string* beginning by O, o, Y or y will be understood > as a "yes" answer.
I think that when this came up in the past, the issue was (at least in part) that this is likely to mask other keybindings unless it's implemented very carefully, which is why it's currently up to the translators to pick a reasonable binding that doesn't conflict with other keys. I don't know how much of an issue this really is, though, since most of the bindings to "Yes" are in modal prompts anyway. It should work fine for the command-line mode, regardless. Also, translators really should be reading README.i18n, as there are several minor quirks in how aptitude expects translations to work, this just being one of them. Daniel
signature.asc
Description: Digital signature
