[PATCH i18n stable] i18n: fix untranslated prompts with translated responses (issue3936)

Wagner Bruna wagner.bruna+mercurial at gmail.com
Mon May 20 18:57:53 CDT 2013

Em 20-05-2013 20:00, Jordi Gutiérrez Hermoso escreveu:
> On 20 May 2013 18:51, Wagner Bruna <wagner.bruna+mercurial at gmail.com> wrote:
>> IMHO we should always accept the English keys, even with translated prompts
>> (to help with muscle memory). And, ideally, detect conflicts at build_mo time.
> Whose muscle memory?

Mine? :-)

More seriously, I occasionally log into machines with different locale
settings, either because it's the default on a just-installed machine or for
supporting users which may or may not prefer translated output.

> It's been a long time since I've actually used software in non-English
> languages, mostly because I got fed up with translations, but for
> people who actually do use those translations, I would expect that
> they might actually have their muscle memory wired to input
> non-English responses to "yes/no"?

Apart from what I mentioned above, software tends to become available only in
English at first, so (at least with Brazilian Portuguese) we need to deal with
a mix of translated and non-translated prompts.

So, when translating prompts, I always avoid reusing the English key for
different options, and prefer simply keeping the keys as they are (sometimes
with ugly "Sim (Y) / Não (N)" cues).


> I wish we had usability studies for this sort of thing...
> - Jordi G. H.

More information about the Mercurial-devel mailing list