Git development
 help / color / mirror / Atom feed
From: "Philip Oakley" <philipoakley@iee.org>
To: "Ralf Thielow" <ralf.thielow@gmail.com>,
	"Thomas Rast" <trast@inf.ethz.ch>
Cc: <jk@jk.gs>, <stimming@tuhh.de>, "Git List" <git@vger.kernel.org>
Subject: Re: [PATCH] l10n: de.po: translate 11 new messages
Date: Mon, 28 Jan 2013 20:33:35 -0000	[thread overview]
Message-ID: <AE5DE037F2E44705AC6716EEB19948B1@PhilipOakley> (raw)
In-Reply-To: 20130128175514.GA2926@rath-ubuntu

From: "Ralf Thielow" <ralf.thielow@gmail.com>
Sent: Monday, January 28, 2013 5:55 PM
> On Mon, Jan 28, 2013 at 11:33:09AM +0100, Thomas Rast wrote:
>> Ralf Thielow <ralf.thielow@gmail.com> writes:
>>
>> >  #: builtin/reset.c:275
>> > -#, fuzzy, c-format
>> > +#, c-format
>> >  msgid "Failed to resolve '%s' as a valid revision."
>> > -msgstr "Konnte '%s' nicht als gültige Referenz auflösen."
>> > +msgstr "Konnte '%s' nicht als gültige Revision auflösen."
>>
>> You don't have "revision" in the glossary[1] yet.  Wouldn't it be
>> appropriate to treat it as "commit", and translate as "Version" to
>> avoid
>> introducing yet another term?
>>
>> Or am I missing some subtle distinction between commit and revision?
>>
>
> I don't think there's a distinction.

It was a problem I had http://stackoverflow.com/a/11792712/717355
answered as:

See "SPECIFYING REVISIONS" of git rev-parse:

  A revision parameter <rev> typically, but not necessarily, names a 
commit object.
  It uses what is called an extended SHA1 syntax, [and includes] various 
ways to spell object names.

It had me confused for a while.

>                 Since we've already translated
> "revision" as "Revision" in a couple of other messages, I'll make a
> new "s/Revision/Version" commit on top.
>
>> Since it's only a single nit, feel free to add my ack when you
>> reroll:
>>
>> Acked-by: Thomas Rast <trast@inf.ethz.ch>
>>
>>
>> [1] https://github.com/ralfth/git-po-de/wiki/Glossary
>>
>> -- 
>> Thomas Rast
>> trast@{inf,student}.ethz.ch
> --
Philip Oakley 

  reply	other threads:[~2013-01-28 20:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-28  6:14 [PATCH] l10n: de.po: translate 11 new messages Ralf Thielow
2013-01-28 10:33 ` Thomas Rast
2013-01-28 17:55   ` Ralf Thielow
2013-01-28 20:33     ` Philip Oakley [this message]
2013-01-29  7:42       ` Ralf Thielow
2013-01-28 16:39 ` Joachim Schmitz
2013-01-28 18:13   ` Ralf Thielow
2013-01-28 20:52     ` Philip Oakley
2013-01-28 18:33 ` [PATCHv2] " Ralf Thielow
2013-01-28 18:33   ` [PATCH] l10n: de.po: translate "revision" consistently as "Version" Ralf Thielow
2013-02-01 18:42     ` [PATCH] l10n: de.po: translate "revision" consistently as "Revision" Ralf Thielow
2013-01-28 18:33   ` [PATCH] l10n: de.po: translate "reset" as "neu setzen" Ralf Thielow

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=AE5DE037F2E44705AC6716EEB19948B1@PhilipOakley \
    --to=philipoakley@iee.org \
    --cc=git@vger.kernel.org \
    --cc=jk@jk.gs \
    --cc=ralf.thielow@gmail.com \
    --cc=stimming@tuhh.de \
    --cc=trast@inf.ethz.ch \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox