All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Pierre-Olivier Vares <pierre-olivier.vares@fingerprint.fr>
Cc: git@vger.kernel.org
Subject: Re: Internationalization and yes/no prompts
Date: Tue, 24 Feb 2015 12:32:35 -0800	[thread overview]
Message-ID: <xmqq1tlfqcd8.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <54EB4B3F.6080706@fingerprint.fr> (Pierre-Olivier Vares's message of "Mon, 23 Feb 2015 16:46:07 +0100")

Pierre-Olivier Vares <pierre-olivier.vares@fingerprint.fr> writes:

> /Supprimer //premier_fichier ? [Remove first_file ?]/
> Natural answer to this question is 'Oui' [Yes], so I type 'o', rather
> than 'y'.
> Once finished, I see no file has been removed (since 'o' has been
> considered as 'different than yes')
> Whereas it's not an end-of-the-world thing*, it's annoying as at first
> sight I didn't understand why it has 'not worked'.
>
> I thought of a few possibilities (some easy to implement, others more
> complex; some are stricter for the user) :

> - explicitly put "y/n" in the message. Translaters should be warned to
> let "y/n",

This may be suboptimal from the end-user's point of view, but it is
the least risky of breaking anything.

And it is way better than the status quo.

> - only allow y and n answers (and variants : yes, no), and reject
> everything else with a message

This is not helpful to the users if it does not say why (O)ui was
rejected, which would mean we would be better off saying [Y/n] in
the message in the first place.

> - use as 'n', but echoes a message : 'Answer considered as /no/'

Unhelpful without stating why (O)ui was considered as 'no'; same
conclusion as above.

> - accept answers depending on the language used to echo the prompt
> (y/n for english, o/n for french, j/n for german, ...)

This would be the best for languages where translations for Yes and
No begin with different letters, but I suspect it might be tricky to
implement.

  reply	other threads:[~2015-02-24 20:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150212085211.9112780692@smtp-out.fingerprint.fr>
2015-02-23 15:46 ` Internationalization and yes/no prompts Pierre-Olivier Vares
2015-02-24 20:32   ` Junio C Hamano [this message]
2015-02-25  9:42     ` Jean-Noël Avila
2015-02-28 15:39     ` [PATCH] Add hint for translators for y/n reply Jean-Noel Avila
2015-03-01  0:18       ` Jiang Xin
2015-03-01  0:30         ` Jiang Xin
2015-03-01  4:02         ` Junio C Hamano
2015-03-01 11:58       ` [PATCHv2] Add hint interactive cleaning Jean-Noel Avila
2015-03-02 19:39         ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqq1tlfqcd8.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=pierre-olivier.vares@fingerprint.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.