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

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

From
Phillip Sz <phillip.szelat@gmail.com>
Date
Sep 19, 2014, 19:11 UTC
Message-ID
<541C7FF7.1020105@gmail.com>
In-Reply-To
<1411146770-8508-2-git-send-email-ralf.thielow@gmail.com>
Hi,
Show 5 quoted lines
>  #: archive.c:351 builtin/archive.c:91
>  msgid "retrieve the archive from remote repository <repo>"
> -msgstr "ruft das Archiv von Remote-Repository <Repository> ab"
> +msgstr "Archiv von Remote-Repository <Repository> abrufen"
> 
"Archiv vom Remote-Repository <Repository> abrufen" sounds better to me.
Show 5 quoted lines
>  #: builtin/add.c:256
>  msgid "record only the fact that the path will be added later"
> -msgstr "speichert nur, dass der Pfad später hinzugefügt werden soll"
> +msgstr "nur speichern, dass der Pfad später hinzugefügt werden soll"
> 

"nur speichern, so dass der Pfad später hinzugefügt werden soll" maybe use a full sentence?

Show 10 quoted lines
>  #: builtin/apply.c:4378
>  msgid "instead of applying the patch, see if the patch is applicable"
> @@ -2472,27 +2472,27 @@ msgstr ""
>  #: builtin/apply.c:4380
>  msgid "make sure the patch is applicable to the current index"
>  msgstr ""
> -"stellt sicher, dass der Patch in der aktuellen Staging-Area angewendet "
> +"sicher stellen, dass der Patch in der aktuellen Staging-Area angewendet "
>  "werden kann"
>  

"stellen Sie sicher, dass der Patch in der aktuellen Staging-Area angewendet " "werden kann" Someone is addressed dirctly.

Phillip
Previous: Ralf ThielowNext: Ralf Thielow
Message 3 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.