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

Re: [PATCH 3/7] part3: l10n: de.po: use imperative form for command options

From
Ralf Thielow <ralf.thielow@gmail.com>
Date
Sep 25, 2014, 18:04 UTC
Message-ID
<CAN0XMO+z-PbcLWO-OS04LeALzDvS5kXsnEB=hZTRGAWhTBVC0g@mail.gmail.com>
In-Reply-To
<54214A4D.8080904@gmail.com>
Hi,
2014-09-23 12:24 GMT+02:00 Phillip Sz <phillip.szelat@gmail.com>:
Show 17 quoted lines
> Hi,
>
>>  #: builtin/describe.c:395
>>  msgid "find the tag that comes after the commit"
>> -msgstr "findet das Tag, das nach Commit kommt"
>> +msgstr "das Tag finden, das nach Commit kommt"
>>
>
> "das Tag finden, das nach dem Commit kommt"
>
>>  #: builtin/fast-export.c:718
>>  msgid "Use the done feature to terminate the stream"
>> -msgstr "Benutzt die \"done\"-Funktion um den Strom abzuschließen"
>> +msgstr "die \"done\"-Funktion benutzen um den Strom abzuschließen"
>>
>
> "die \"done\"-Funktion benutzen, um den Strom abzuschließen"

You send a patch for the comma before "um" (thanks for that). I'll rebase these patches on top of that before applying, so the comma will be added then.

>
> Maybe its better to use »Stream» instead of »Strom« in general?
>
What about "Datenstrom"?
> Phillip
>
>
Previous: Phillip SzNext: phillip
Message 10 of 24 in “l10n: de.po: use imperative form for command options”
  1. 0/7 l10n: de.po: use imperative form for command optionsRalf Thielow, Sep 19, 2014
  2. 1/7 part1: l10n: de.po: use imperative form for command optionsRalf Thielow, Sep 19, 2014
  3. Phillip SzSep 19, 2014
  4. Ralf ThielowSep 19, 2014
  5. part1: l10n: de.po: use imperative form for command optionsRalf Thielow, Oct 24, 2014
  6. phillipOct 25, 2014
  7. 2/7 part2: l10n: de.po: use imperative form for command optionsRalf Thielow, Sep 19, 2014
  8. 3/7 part3: l10n: de.po: use imperative form for command optionsRalf Thielow, Sep 19, 2014
  9. Phillip SzSep 23, 2014
  10. Ralf ThielowSep 25, 2014
  11. phillipSep 25, 2014
  12. part3: l10n: de.po: use imperative form for command optionsRalf Thielow, Oct 24, 2014
  13. 4/7 part4: l10n: de.po: use imperative form for command optionsRalf Thielow, Sep 19, 2014
  14. 5/7 part5: l10n: de.po: use imperative form for command optionsRalf Thielow, Sep 19, 2014
  15. 6/7 part6: l10n: de.po: use imperative form for command optionsRalf Thielow, Sep 19, 2014
  16. 7/7 part7: l10n: de.po: use imperative form for command optionsRalf Thielow, Sep 19, 2014
  17. 0/7 use imperative form for commandRalf Thielow, Nov 7, 2014
  18. 1/7 part1: l10n: de.po: use imperative form for command optionsRalf Thielow, Nov 7, 2014
  19. 2/7 part2: l10n: de.po: use imperative form for command optionsRalf Thielow, Nov 7, 2014
  20. 3/7 part3: l10n: de.po: use imperative form for command optionsRalf Thielow, Nov 7, 2014
  21. 4/7 part4: l10n: de.po: use imperative form for command optionsRalf Thielow, Nov 7, 2014
  22. 5/7 part5: l10n: de.po: use imperative form for command optionsRalf Thielow, Nov 7, 2014
  23. 6/7 part6: l10n: de.po: use imperative form for command optionsRalf Thielow, Nov 7, 2014
  24. 7/7 part7: l10n: de.po: use imperative form for command optionsRalf Thielow, Nov 7, 2014

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.