git@vger.kernel.org mailing list mirror (one of many)
 help / Atom feed
From: Martin Ågren <martin.agren@gmail.com>
To: Changwoo Ryu <cwryu@debian.org>
Cc: Junio C Hamano <gitster@pobox.com>, Jean-Noël AVILA <jn.avila@free.fr>, Stefan Beller <sbeller@google.com>, "brian m. carlson" <sandals@crustytoothpaste.net>, Philip Oakley <philipoakley@iee.org>, Git Mailing List <git@vger.kernel.org>, Jiang Xin <worldhello.net@gmail.com>, Alexander Shopov <ash@kambanaria.org>, Jordi Mas <jmas@softcatala.org>, Ralf Thielow <ralf.thielow@gmail.com>, Christopher Díaz <christopher.diaz.riv@gmail.com>, Marco Paolone <marcopaolone@gmail.com>, Vasco Almeida <vascomalmeida@sapo.pt>, Dimitriy Ryazantcev <DJm00n@mail.ru>, Peter Krefting <peter@softwolves.pp.se>, Trần Ngọc Quân <vnwildman@gmail.com>, Jacques Viviers <jacques.viviers@gmail.com>, m4sk1n <m4sk1n@o2.pl>
Subject: Re: [PATCH] submodule: avoid sentence-lego in translated string
Date: Tue, 10 Oct 2017 20:14:44 +0200
Message-ID: <CAN0heSoetaKFsZ8b0kD5w=G4g3GJJHWwBzR9RreEQoaJz_YnTg@mail.gmail.com> (raw)
In-Reply-To: <CAEe2ifX5+OUOWw75pFZN86pT1iwYk2vb6u+uEMYLDpxYzmJLEQ@mail.gmail.com>

On 10 October 2017 at 04:35, Changwoo Ryu <cwryu@debian.org> wrote:
> 2017-10-10 10:26 GMT+09:00 Junio C Hamano <gitster@pobox.com>:
>> Jean-Noël AVILA <jn.avila@free.fr> writes:
>>
>>> On Monday, 9 October 2017, 09:47:26 CEST Stefan Beller wrote:
>>>
>>>> I always assumed that translators are aware of these issues and sort of
>>>> work around this somehow, maybe like this:
>>>>
>>>>   "submodule entry '%s' (%s) is not a commit. It is of type %s"
>>>
>>> Translators can be aware of the issue if the coder commented the
>>> internationalization string with some possible candidates for the placeholders
>>> when it is not clear unless you check in the source code. Much effort was
>>> poured into translating the technical terms in other parts of Git; it seems
>>> awkward to just step back in this occurence.
>>
>> I do not see this particular case as "stepping back", though.
>>
>> Our users do not spell "git cat-file -t commit v2.0^{commit}" with
>> 'commit' translated to their language, right?  Shouldn't an error
>> message output use the same phrase the input side requests users to
>> use?

I thought Jean-Noël meant at least partially the translator-experience,
not just the user-experience, but I might be wrong.

I prepared a patch to give a TRANSLATORS:-comment, but then I realized
that we have more instances like this with `typename()`. Actually, quite
often we avoid the issue (intentionally or unintentionally) by writing
"of type %s", but other times, we do the "is a %s". So I don't know,
maybe it all works anyway. The regular translators have now received 10
mails (11 counting this) so might be aware of this particular string by
now. :-/

> Users know the limit of command-line translation. They type "commit"
> to commit but they see translated "commit" in output messages. It is
> actually confusing. But the untranslated English literals in the
> middle of translated sentences does not remove the confusion but
> increase it in a different way.

What you describe seems plausible, but I have to admit that I don't use
i18n-ized software myself.

Martin

  reply index

Thread overview: 13+ messages in thread (expand / mbox.gz / Atom feed / [top])
2017-10-08  7:38 [L10N] Kickoff of translation for Git 2.15.0 round 1 Jiang Xin
2017-10-08  8:48 ` [PATCH] submodule: avoid sentence-lego in translated string Martin Ågren
2017-10-08  9:32   ` Philip Oakley
2017-10-08 10:26     ` Martin Ågren
2017-10-09  0:51     ` brian m. carlson
2017-10-09  1:30       ` Junio C Hamano
2017-10-09  4:14         ` Martin Ågren
2017-10-09 16:47           ` Stefan Beller
2017-10-09 21:11             ` Jean-Noël AVILA
2017-10-10  1:26               ` Junio C Hamano
2017-10-10  2:35                 ` Changwoo Ryu
2017-10-10 18:14                   ` Martin Ågren [this message]
2017-10-08 12:18 ` [PATCH] i18n: add a missing space in message Jean-Noel Avila

Reply instructions:

You may reply publically 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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to='CAN0heSoetaKFsZ8b0kD5w=G4g3GJJHWwBzR9RreEQoaJz_YnTg@mail.gmail.com' \
    --to=martin.agren@gmail.com \
    --cc=DJm00n@mail.ru \
    --cc=ash@kambanaria.org \
    --cc=christopher.diaz.riv@gmail.com \
    --cc=cwryu@debian.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jacques.viviers@gmail.com \
    --cc=jmas@softcatala.org \
    --cc=jn.avila@free.fr \
    --cc=m4sk1n@o2.pl \
    --cc=marcopaolone@gmail.com \
    --cc=peter@softwolves.pp.se \
    --cc=philipoakley@iee.org \
    --cc=ralf.thielow@gmail.com \
    --cc=sandals@crustytoothpaste.net \
    --cc=sbeller@google.com \
    --cc=vascomalmeida@sapo.pt \
    --cc=vnwildman@gmail.com \
    --cc=worldhello.net@gmail.com \
    /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

git@vger.kernel.org mailing list mirror (one of many)

Archives are clonable:
	git clone --mirror https://public-inbox.org/git
	git clone --mirror http://ou63pmih66umazou.onion/git
	git clone --mirror http://czquwvybam4bgbro.onion/git
	git clone --mirror http://hjrcffqmbrq6wope.onion/git

Newsgroups are available over NNTP:
	nntp://news.public-inbox.org/inbox.comp.version-control.git
	nntp://ou63pmih66umazou.onion/inbox.comp.version-control.git
	nntp://czquwvybam4bgbro.onion/inbox.comp.version-control.git
	nntp://hjrcffqmbrq6wope.onion/inbox.comp.version-control.git
	nntp://news.gmane.org/gmane.comp.version-control.git

 note: .onion URLs require Tor: https://www.torproject.org/
       or Tor2web: https://www.tor2web.org/

AGPL code for this site: git clone https://public-inbox.org/ public-inbox