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

Re: [PATCH] l10n: add framework for localizing the manpages

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 15, 2017, 16:07 UTC
Message-ID
<xmqqr31yfrre.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<0ae83f7f-e178-31b3-87ea-324e3f00d469@free.fr>
Jean-Noël Avila <jn.avila@free.fr> writes:
Show 22 quoted lines
> Le 13/03/2017 à 01:01, Junio C Hamano a écrit :
>> +#. type: Plain text
>>> +#: git-add.txt:15
>>> +#, no-wrap
>>> +msgid ""
>>> +"'git add' [--verbose | -v] [--dry-run | -n] [--force | -f] [--interactive | -i] [--patch | -p]\n"
>>> +"\t  [--edit | -e] [--[no-]all | --[no-]ignore-removal | [--update | -u]]\n"
>>> +"\t  [--intent-to-add | -N] [--refresh] [--ignore-errors] [--ignore-missing]\n"
>>> +"\t  [--chmod=(+|-)x] [--] [<pathspec>...]\n"
>>> +msgstr ""
>>> +"'git add' [-n] [-v] [--force | -f] [--interactive | -i] [--patch | -p]\n"
>>> +"\t  [--edit | -e] [--[no-]all | --[no-]ignore-removal | [--update | -u]]\n"
>>> +"\t  [--intent-to-add | -N] [--refresh] [--ignore-errors] [--ignore-missing]\n"
>>> +"\t  [--] [<chemin>...]\n"
>> This shows that even after adding just _one_ new option to the
>> ...  A mere single
>> rephrasing of a word in a large paragraph would have to result in
>> the entire paragraph to be translated again?
>
> I'm not sure to clearly understand your point: if there is the
> introduction of a new option, there is a need to update the translation
> for sure.

You probably are used to po4a well enough to accept "the smallest unit of translation is paragraph" as a natural given, and it may be an acceptable way to work for those who actually do the translation.

Because I am not used to po4a and I don't do translation, "why I have to update the above translation of the whole paragraph, in response to a patch to rename just a single option", e.g.

	-	[--edit | -e] [--no-]all | --[no-]ignore-removal | [--update | -u]]
	+	[--edit | -e] [--no-]all | --[no-]ignore-removal | [--modify | -m]]

was a natural reaction for me. In any case, I won't be doing the translations, and those who work with po4a are happy with the tool, that is fine by me.

Previous: Jean-Noël AvilaNext: Stefan Beller
Message 10 of 37 in “l10n: add framework for localizing the manpages”
  1. l10n: add framework for localizing the manpagesJean-Noel Avila, Mar 12, 2017
  2. l10n: add framework for localizing the manpagesJean-Noel Avila, Mar 12, 2017
  3. Jean-Noël AVILAMar 12, 2017
  4. Junio C HamanoMar 13, 2017
  5. Ævar Arnfjörð BjarmasonMar 14, 2017
  6. Junio C HamanoMar 14, 2017
  7. Jean-Noël AvilaMar 15, 2017
  8. Ævar Arnfjörð BjarmasonMar 15, 2017
  9. Jean-Noël AvilaMar 15, 2017
  10. Junio C HamanoMar 15, 2017
  11. Stefan BellerMar 15, 2017
  12. 1/2 l10n: Introduce framework for localizing man pagesJean-Noel Avila, Mar 18, 2017
  13. 2/2 l10n: Add git-add.txt to localized man pagesJean-Noel Avila, Mar 18, 2017
  14. Junio C HamanoMar 18, 2017
  15. Jean-Noël AVILAMar 18, 2017
  16. Junio C HamanoMar 18, 2017
  17. Junio C HamanoMar 20, 2017
  18. Jean-Noël AvilaMar 20, 2017
  19. Jean-Noël AVILAMar 20, 2017
  20. Junio C HamanoMar 20, 2017
  21. Rework manpage localisationJean-Noel Avila, Mar 20, 2017
  22. 2/2 l10n: Add git-add.txt to localized man pagesJean-Noel Avila, Mar 20, 2017
  23. Junio C HamanoMar 20, 2017
  24. Jean-Noël AvilaMar 22, 2017
  25. Junio C HamanoMar 22, 2017
  26. Stefan BellerMar 22, 2017
  27. Junio C HamanoMar 22, 2017
  28. Stefan BellerMar 22, 2017
  29. Michael J GruberMar 24, 2017
  30. Jean-Noël AVILAMar 25, 2017
  31. Junio C HamanoMar 26, 2017
  32. Jean-Noël AVILAMar 27, 2017
  33. Junio C HamanoMar 27, 2017
  34. Ævar Arnfjörð BjarmasonMar 24, 2017
  35. Junio C HamanoMar 24, 2017
  36. 1/2 l10n: Introduce framework for localizing man pagesJean-Noel Avila, Mar 20, 2017
  37. Junio C HamanoMar 21, 2017

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.