git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] l10n: de.po: translate 11 new messages

From
Ralf Thielow <ralf.thielow@gmail.com>
Date
Jan 29, 2013, 07:42 UTC
Message-ID
<CAN0XMOK6PMCC-Cr9cX9a3ng6+gijAOTQf2WmxyTXXpZ2TvR3Cg@mail.gmail.com>
In-Reply-To
<AE5DE037F2E44705AC6716EEB19948B1@PhilipOakley>
2013/1/28 Philip Oakley <philipoakley@iee.org>:
Show 37 quoted lines
> 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.
>

Thanks. So it would be a mistake to translate "revision" and "commit" with the same word. This would hide the special meaning of revision and the user wouldn't see that there's a difference.

I'll amend the commit which unifys the translation of "revision" and "commit" in the way that "revision" will be translated as "Revision" in the whole file. I'll also update the glossary.

Show 19 quoted lines
>>                 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
Previous: Philip OakleyNext: Joachim Schmitz
Message 5 of 12 in “l10n: de.po: translate 11 new messages”
  1. l10n: de.po: translate 11 new messagesRalf Thielow, Jan 28, 2013
  2. Thomas RastJan 28, 2013
  3. Ralf ThielowJan 28, 2013
  4. Philip OakleyJan 28, 2013
  5. Ralf ThielowJan 29, 2013
  6. Joachim SchmitzJan 28, 2013
  7. Ralf ThielowJan 28, 2013
  8. Philip OakleyJan 28, 2013
  9. [PATCHv2] l10n: de.po: translate 11 new messagesRalf Thielow, Jan 28, 2013
  10. l10n: de.po: translate "revision" consistently as "Version"Ralf Thielow, Jan 28, 2013
  11. l10n: de.po: translate "revision" consistently as "Revision"Ralf Thielow, Feb 1, 2013
  12. l10n: de.po: translate "reset" as "neu setzen"Ralf Thielow, Jan 28, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.