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

login
register
mail settings
Submitter Kevin Bullock
Date May 16, 2013, 2:37 a.m.
Message ID <fc1c4221dd82de958b9b.1368671856@slower-than-infinity.lan>
Download mbox | patch
Permalink /patch/1656/
State Accepted
Commit 15aef461facdeaf3f8cc42b6d6c95e0768537d84
Headers show

Comments

Kevin Bullock - May 16, 2013, 2:37 a.m.
# HG changeset patch
# User Kevin Bullock <kbullock@ringworld.org>
# Date 1368671779 18000
#      Wed May 15 21:36:19 2013 -0500
# Branch stable
# Node ID fc1c4221dd82de958b9be5f05c57622679625d21
# Parent  278057693a1ddb93f95fa641e30e7a966ac98434
i18n: fix untranslated prompts with translated responses (issue3936)
Matt Mackall - May 16, 2013, 6:58 p.m.
On Wed, 2013-05-15 at 21:37 -0500, Kevin Bullock wrote:
> # HG changeset patch
> # User Kevin Bullock <kbullock@ringworld.org>
> # Date 1368671779 18000
> #      Wed May 15 21:36:19 2013 -0500
> # Branch stable
> # Node ID fc1c4221dd82de958b9be5f05c57622679625d21
> # Parent  278057693a1ddb93f95fa641e30e7a966ac98434
> i18n: fix untranslated prompts with translated responses (issue3936)

Queued for stable, thanks.

I'd like to see a consensus among translators on how to do this.

I also thing we should unify all the string args used by prompt() into a
single string so that translators have the full context.
Wagner Bruna - May 20, 2013, 10:51 p.m.
Em 16-05-2013 15:58, Matt Mackall escreveu:
> On Wed, 2013-05-15 at 21:37 -0500, Kevin Bullock wrote:
>> # HG changeset patch
>> # User Kevin Bullock <kbullock@ringworld.org>
>> # Date 1368671779 18000
>> #      Wed May 15 21:36:19 2013 -0500
>> # Branch stable
>> # Node ID fc1c4221dd82de958b9be5f05c57622679625d21
>> # Parent  278057693a1ddb93f95fa641e30e7a966ac98434
>> i18n: fix untranslated prompts with translated responses (issue3936)
> 
> Queued for stable, thanks.
> 
> I'd like to see a consensus among translators on how to do this.

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.

> I also thing we should unify all the string args used by prompt() into a
> single string so that translators have the full context.

Seems like a good approach (as long as we ensure there's no paragraph boundary
on that single string, of course).

Regards,
Wagner
Jordi Gutiérrez Hermoso - May 20, 2013, 11 p.m.
On 20 May 2013 18:51, Wagner Bruna <wagner.bruna+mercurial@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?

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"?

I wish we had usability studies for this sort of thing...

- Jordi G. H.
Wagner Bruna - May 20, 2013, 11:57 p.m.
Em 20-05-2013 20:00, Jordi Gutiérrez Hermoso escreveu:
> On 20 May 2013 18:51, Wagner Bruna <wagner.bruna+mercurial@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).

Regards,
Wagner

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

Patch

diff --git a/i18n/de.po b/i18n/de.po
--- a/i18n/de.po
+++ b/i18n/de.po
@@ -14078,13 +14078,14 @@  msgstr ""
 
 #, python-format
 msgid "was merge of '%s' successful (yn)?"
-msgstr ""
+msgstr "ist die Zusammenführung von '%s' gelungen (jn)?"
 
 #, python-format
 msgid ""
 " output file %s appears unchanged\n"
 "was merge successful (yn)?"
-msgstr ""
+msgstr "Ausgabedatei %s scheint unverändert\n"
+"ist die Zusammenführung gelungen (jn)?"
 
 msgid "unterminated string"
 msgstr "nicht abgeschlossene Zeichenkette"