-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi Ted,

On 26/03/2012 13:57, Ted Ts'o wrote:
> On Fri, Mar 23, 2012 at 10:27:11PM -0400, David Prévot wrote:
>>
>> We noticed some tiny errors in the mke2fs.conf.5 and tune2fs.8 manpages

> Thanks, applied.

Thanks.

>> BTW, we would be pleased if you could consider shipping the translated
>> manpages directly in your package, or even better, help us to integrate
>> them upstream.
> 
> The major concern that I have with including the translated manpages
> is the synchronization problem that this implies.

We use po4a in order to maintain them: if a string change or is added,
the translated manpage will automatically (at build time) include the
original string instead if the PO file has not been updated.

> By definition the
> translated man pages will always be out of sync, whenever I make
> change;

Well, it's just a matter of coordination, as in every project. As if you
changed some debconf template, you're welcome to send a call for
translation before uploading the package in order to get them updated
when it goes public (podebconf-report-po can even be used for other kind
of translations, like manpage translations, with the --notdebconf
switch). Other project (e.g. http://translationproject.org/) can also
come handy to handle upstream translations (e.g. man-db runtime and
documentation are handled there).

> I can forsee this leading to endless bug reports, for which I
> am not really able to act upon.  Also, how do the man pages get
> updated?  Do I have to ask?  Will someone be checking the e2fsprogs
> git repository on a regular basis to find man page changes?

If you're willing to include the translated manpages inside the (Debian
or upstream) project, I'd be happy to offer my help in order to deal
with the translation handling (e.g. subscribing to the PTS and thus the
BTS, developer lists, etc.) in order to stay tuned and be able to make
sure the translations are updated in due time. Of course, a friendly
reminder once in a while (e.g. “we are considering uploading version X.Y
in two weeks”) can just be enough in some case.

> The other question I have is if I include the French man pages in the
> e2fsprogs package, then what if I start having to include German,
> Spanish, Polish, Turkish, etc.

That would be an awesome improvement, and I would be really happy to
help you in that regard (thus my above proposal to “deal with the
translation handling”). If you're not willing to push an extra burden on
your shoulders to deal with translators (which is a fair statement,
thanks for sharing your concerns), I for sure would be willing to help.

> Wouldn't this massively bloat the
> e2fsprogs package? And if I have to create an e2fsprogs-fr-manpages,
> and a e2fsrpogs-es-manpages, etc.

If it's too much of a bloat, simply splitting the translations (will it
be only the manpages, or both the manpages and the runtime translations)
in one separate package (à la util-linux-locales) could do the trick,
one package by language looks a bit overkill at first sight (but the
idea can be kept for later if needed).

> again this start looking like a
> huge amount of work just to give me more bug reports that I'm not
> capable of handling (since I don't speak French.)

Thus my offer to help.

Regards

David

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJPcMFQAAoJELgqIXr9/gnysiwP/Rwx7+HrhxohKCIIbFWxECme
RfXQyH6lil7Dzcd8SArc3HrSu7asyZmR2z+exGYjxTKTnnCNIyntW+3rtdC2Y453
av0fUim1lBgZXl6eHVDxWjEDAQEexVgNgEyrRbib73E/6yJhs42tgBrZAnyvdPVl
deCpOcLBvRhOj0VwqEZXfTHQU9diNe081AzM4rUvUJIRQhhS8lt83KYi1O6+kMBz
HJmFg+3UIiE83xnlKTmBOsdDDc8ExOjVoVQ4SgfWrcXA4KenGXhluXhc3UMnkVAl
u9eHwJA/puq+0nUAIaXtNVjZcHsVQoDW/ABuBwUSZkdWDDsiexlENL1TeJVu0jL8
hmvWdVuwXJ+Jp1rfxcd3sUM2tndhXPRAxXNZ+LSewBvby1P6KkL6cPff+07ns0oy
fOfYZ7aeSRdyH1YV3kpotv0aBJ7Arov+NNtiMRMpqrSnT+kE7A1TNdJ/6NN91mum
K3hpAXjIf1fu5AJpWQGDhUzohZvGPB5iVd1bmOw9jBpFREun41pFoD8mKf5ZR686
BWnD4GQz9GQzOJ2hChUMoGnoXGg/PF6j4dDKgauh2Bcv+ddh1RPpw8+rhqYh3Lq4
yoBu79F2pwGGxJoD1Ff/G2ffiu9o8/pSci2bFEaS4SrohDZXG0hFIwWxBqc4QSaQ
oIsV+Q52/v9qVCbheUBi
=ouR1
-----END PGP SIGNATURE-----



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to