git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Martin Ågren" <martin.agren@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "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>,
	"Jean-Noël Avila" <jn.avila@free.fr>,
	"Marco Paolone" <marcopaolone@gmail.com>,
	"Changwoo Ryu" <cwryu@debian.org>,
	"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>, "Stefan Beller" <sbeller@google.com>
Subject: Re: [PATCH] submodule: avoid sentence-lego in translated string
Date: Mon, 9 Oct 2017 06:14:12 +0200	[thread overview]
Message-ID: <CAN0heSqFSiev8BeZVu3KBA5vswsbQrrOH=tYYOSs_h_eq=8-3Q@mail.gmail.com> (raw)
In-Reply-To: <CAPc5daVk+sPLmw4G_AghOVFeO5myKTADQjKr823U3xaQZK+43g@mail.gmail.com>

On 9 October 2017 at 03:30, Junio C Hamano <gitster@pobox.com> wrote:
> On Mon, Oct 9, 2017 at 9:51 AM, brian m. carlson
> <sandals@crustytoothpaste.net> wrote:
>> On Sun, Oct 08, 2017 at 10:32:35AM +0100, Philip Oakley wrote:
>>> From: "Martin Ågren" <martin.agren@gmail.com>
>>> > - die(_("submodule entry '%s' (%s) is a %s, not a commit"),
>>> > -     cb->path, oid_to_hex(oid), typename(type));
>>> > + die(_("submodule entry '%s' (%s) is not a commit"),
>>> > +     cb->path, oid_to_hex(oid));
>>> Bikeshed,
>>> maybe:
>>> "submodule entry '%s' (%s) is not a commit. It is a %s"
>>> This puts the two parts in separate sentences?
>>
>> Languages with multiple grammatical genders are going to have problems
>> with this.  In French, "a tree" is "un arbre" (masculine), but "a tag"
>> is "une étiquette" (feminine).  We don't currently have a Spanish
>> translation, but this would break there as well.
>>
>> Splitting the article out with the type name is still problematic for
>> languages where articles vary by case, like German, since the
>> translation might be reused in another place requiring a different case.
>
> While all of the above is correct, would we really need to subject typename()
> to translation? IOW, can't we just treat 'blob', 'tree', 'commit' and
> 'tag' as-is,
> as terms of art (i.e. with a specific or precise meaning within a
> given discipline
> or field and might have a different meaning in common usage)?

In another subthread, I sort of suggested "... is of type '%s', not 'commit'".
So "commit" and "%s" would appear as the file-format-level terms that they are.
I think it looks odd but I guess it might work in Swedish, FWIW.

In this particular case, we could have three specific messages plus one default
message (which at the time shouldn't ever occur). Or we have one specific
message for the "tag"-case, which seems to have been Stefan's original
motivation, and a generic message for the other cases.

  reply	other threads:[~2017-10-09  4:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  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 [this message]
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
2017-10-08 12:18 ` [PATCH] i18n: add a missing space in message Jean-Noel Avila

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

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

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

  git send-email \
    --in-reply-to='CAN0heSqFSiev8BeZVu3KBA5vswsbQrrOH=tYYOSs_h_eq=8-3Q@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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).