German translation interferes with record extension
timeless at gmail.com
Wed Sep 28 14:15:55 CDT 2011
This sort of problem is not at all unexpected.
Fwiw, when Microsoft redid their English UI (for Vista iirc), they
worked to retain key compatibility or ensure harmless behavior:
In wXP, trying to close a dirty notepad session asked:
Do you want to save?
*&yes (enter, space) / &no / cancel (esc)
In wVista, you get roughly:
What do you want to do?
*Save (enter, space)
I think we could enforce those rules:
1. If replacing a key, the new key must not be used for another
behavior in the primary locale (and should not be used for a different
behavior in a commonly used locale)
2. Default actions should not change across localizations
Note that there is a convention of adding (&n) for an access key not
present in a localized string, it's mostly possible to do this (some
pain ensues with rtl locales, but they should provide the key to avoid
And yes, it isn't uncommon to use a translated ui with an En keyboard.
One thing that could be done is to support two keys (localized and
En), but then you have to ensure there isn't a modality conflict
between them, plus it complicates the code.
On 9/28/11, Meikel Brandmeyer <mb at kotka.de> wrote:
> Dear Mercurial devs,
> I encountered an issue with record in 1.9.2.
> What I did:
> I started a record session, added some hunks and pushed "d" to skip over the
> remaining changes and files.
> What I expected:
> That exactly that happens and the commit message editor pops up.
> What happened:
> The next file got added to the changes to be committed.
> Thanks to Matt Mackall on #mercurial I found the culprit in the german
> locale settings.
> The command keys are also translated. However this is neither shown by the
> prompt of record nor by the help message which is accessible via ?. To add
> to the confusion the keys are also translated inconsistently. d and f
> basically flip their meaning, but y and n are *not* translated! So with y
> working as usual and the wrong prompt menu one has no indication whatsoever
> that the keys might be translated.
> So there are two issues here: the keys are not translated consistently and
> record doesn't give a hint (neither in the prompt nor in the help message)
> that the keys actually are translated.
> As a side note: Maybe translating the keys should be reconsidered. It is
> perfectly reasonable to have non-english locale setting but at same time
> have an american keyboard layout. By translating eg. &Skip to &Überspringen
> you basically disable skipping of changes because you can't type ü on an
> american keyboard.
> Mercurial-devel mailing list
> Mercurial-devel at selenic.com
Sent from my mobile device
More information about the Mercurial-devel