On Tue, Feb 12, 2008 at 09:24:33PM +0100, Christian Perrier <[EMAIL PROTECTED]> was heard to say: > Quoting Andrey ([EMAIL PROTECTED]): > > Хотите продолжить? [Д/н/?] н > > Неверный ответ. Введите допустимую команду или '?' для справки. > > Хотите продолжить? [Д/н/?] n > > Прервать. > > > > As you can see, aptitude tries hard to be polite and asks my > > confirmation in my native language. I appreciate it and answer in > > Russian too, but aptitude doesn't understand what I say :-( > > > > From the PO file: > > #: src/cmdline/cmdline_prompt.cc:910 > msgid "Do you want to continue? [Y/n/?] " > msgstr "Хотите продолжить? [Д/н/?] " > > and later: > > #: src/ui.cc:2908 > msgid "yes_key" > msgstr "y" > > #: src/ui.cc:2909 > msgid "no_key" > msgstr "n" > > > This is where the confusion comes from. The Russian translator did put > "y" as "Yes key" and "n" as "No key" instead of Д and н.
That is a problem, but it won't fix this particular case, since the prompt in question doesn't use a localized technique to test whether the user entered Y or N. This is complicated by the fact that this is not solely a yes/no prompt; otherwise I could use rpmatch(3) to localize it. There are a good half-dozen possible characters the user can enter, and odds are that some of them are abbreviations for "yes" or "no" in some language. I'm not sure what the best approach is; maybe yet another bunch of tagged localized strings that control recognized responses to prompts? Daniel
