German translation interferes with record extension

Meikel Brandmeyer mb at
Sun Oct 2 15:33:13 CDT 2011


Am 01.10.2011 um 02:06 schrieb Wagner Bruna:

> In my experience, applications that try to support both translated and
> untranslated keys are easier to use. In Portuguese, for instance, some prompts
> accept both 's' ("sim") and 'y' for "yes". I personally dislike key
> translations (I think of those as one-letter commands, and translating
> commands doesn't make any sense), but they *are* helpful for users that do not
> understand English very well.
> So IMHO the code should always accept the original untranslated keys, and
> additionally distinct keys suggested by the current translation. On the other
> hand, the documentation should always mention the original keys, since we
> never know if a particular prompt text translation will be available.

How would that work? The german translation (in this specific case) basically swaps the meaning of f and d for the record commands. So it's either or in this case. Accepting both won't work. And in this case I would prefer non-translated keys. The help menu is right there in case of harder to memorize non-translated keys.

But on the other hand I'm in close contact with english all day at work. So maybe I'm not the right person to ask.

My 0.02€.


More information about the Mercurial-devel mailing list