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

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

From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date
Mar 15, 2017, 09:01 UTC
Message-ID
<CACBZZX7CoEn0d01hU=A5RbDiNwQi0wUJM9mU25pPnqTPu05r+w@mail.gmail.com>
In-Reply-To
<103dec84-b274-0a81-fa9b-bf29afd988d9@free.fr>
On Wed, Mar 15, 2017 at 9:11 AM, Jean-Noël Avila <jn.avila@free.fr> wrote:
Show 21 quoted lines
> Le 14/03/2017 à 22:00, Ævar Arnfjörð Bjarmason a écrit :
>> On Mon, Mar 13, 2017 at 1:01 AM, Junio C Hamano <gitster@pobox.com> wrote:
>>> Jean-Noel Avila <jn.avila@free.fr> writes:
>> Jean: Comments on the patch:
>>
>> - Firstly thanks for working on this. When I hacked up the initial po
>> support in v1.7.8-rc2-1-g5e9637c629 I always meant to try out po4a,
>> but never got around to it. It's much easier than I thought.
>
> Well, that's only the simplest setup I could come up with :-). I'm
> discovering the tool and it seems that can go quite hairy, depending on
> where we want to go.
>
>> - Consider submitting a more minimal patch that doesn't have the giant
>> fr.po (or just some minor cut version) as the tip of the series, to
>> make this easier to review
>
> OK. Will split in po4a.conf + Makefile changes, then pot and po files.
> The point is that as long as the po files are not translated at a
> minimum level, po4a does not generate the target files. Right now, the
> threshold is 80% of translated strings (no fuzzy).

Right, I don't mean don't include it, just add the *.pot and *.po file in a subsequent patch, so reviewers focusing just on the translation infra changes have a ~100-200 line patch to look at instead of 10x that.

Show 6 quoted lines
>> - The git-add.txt file is hardcoded in po4a.conf, won't this file need
>> to be generated in some final version of this series?
>
> If all the translation string are harvested automatically from the
> source files, the resulting po file will be huge. For the moment, I
> prefered to manually select the files and check that po4a behaves correctly.
Yeah, makes sense, we can just start with git-add.txt and add more files later.
Previous: Jean-Noël AvilaNext: Jean-Noël Avila
Message 8 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.