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

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

From
Thomas Rast <tr@thomasrast.ch>
Date
Feb 8, 2014, 18:39 UTC
Message-ID
<877g95motv.fsf@thomasrast.ch>
In-Reply-To
<1390511452-6553-1-git-send-email-ralf.thielow@gmail.com>
I see you are defining new glossary terms:
  shallow     unvollständig
  grafted     gesondert eingehängt

I guess the first one is reasonable if we don't call anything "incomplete"? (I don't think we do, just checking.)

I don't really like 'gesondert eingehängt', how about 'transplantiert' instead? Or just say graft=Graft and use 'mit Grafts' or some similar workaround, since it is a highly specialized term.

Ralf Thielow <ralf.thielow@gmail.com> writes:
Show 8 quoted lines
>  #: diff.c:113
>  #, c-format
> @@ -975,21 +975,23 @@ msgid ""
>  "There is nothing to exclude from by :(exclude) patterns.\n"
>  "Perhaps you forgot to add either ':/' or '.' ?"
>  msgstr ""
> +"Es gibt nichts, was durch :(exclude) Muster ausgeschlossen wird.\n"
> +"Vielleicht haben Sie vergessen entweder ':/' oder '.' hinzuzufügen?"

Doesn't sound right -- the original seems to describe the situation where you are using :(exclude) without any non-excluded paths, whereas the German first sentence sounds like you are using :(exclude) when it doesn't match any paths.

Perhaps it works if translated very liberally:

":(exclude) Muster, aber keine anderen Pfadspezifikationen angegeben.\n" "Vielleicht haben Sie vergessen entweder ':/' oder '.' hinzuzufügen?"

Show 6 quoted lines
>  #: remote.c:753
> -#, fuzzy, c-format
> +#, c-format
>  msgid "Cannot fetch both %s and %s to %s"
> -msgstr "Kann keine Commit-Beschreibung für %s bekommen"
> +msgstr "Kann 'fetch' nicht für %s und %s nach %s ausführen."
[...]
Show 5 quoted lines
>  #: remote.c:761
>  #, c-format
>  msgid "%s tracks both %s and %s"
> -msgstr ""
> +msgstr "%s folgt %s und %s"

In both of these the key point is "both". Perhaps use "sowohl... als auch".

Show 5 quoted lines
>  #: wt-status.c:275
> -#, fuzzy
>  msgid "new file"
> -msgstr "neue Datei:   %s"
> +msgstr "neue Datei:"
[...]
Show 11 quoted lines
>  #: wt-status.c:285
> -#, fuzzy
>  msgid "typechange"
> -msgstr "Typänderung: %s"
> +msgstr "Typänderung:"
>  
>  #: wt-status.c:287
> -#, fuzzy
>  msgid "unknown"
> -msgstr "unbekannt:    %s"
> +msgstr "unbekannt:"
Do we still need the trailing colon?
-- 
Thomas Rast
tr@thomasrast.ch
Previous: Ralf ThielowNext: David Kastrup
Message 9 of 16 in “l10n: de.po: translate 27 new messages”
  1. l10n: de.po: translate 27 new messagesRalf Thielow, Jan 23, 2014
  2. Jiang XinJan 24, 2014
  3. l10n: de.po: translate 27 new messagesRalf Thielow, Jan 27, 2014
  4. l10n: de.po: translate 28 new messagesRalf Thielow, Feb 5, 2014
  5. l10n: de.po: translate 28 new messagesRalf Thielow, Feb 8, 2014
  6. David KastrupFeb 8, 2014
  7. Ralf ThielowFeb 8, 2014
  8. l10n: de.po: translate 28 new messagesRalf Thielow, Feb 8, 2014
  9. Thomas RastFeb 8, 2014
  10. David KastrupFeb 8, 2014
  11. Thomas RastFeb 8, 2014
  12. David KastrupFeb 8, 2014
  13. Ralf ThielowFeb 8, 2014
  14. David KastrupFeb 8, 2014
  15. Ralf ThielowFeb 8, 2014
  16. l10n: de.po: correct message when hiding commits by craftRalf Thielow, Feb 8, 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.