Le 26/07/2010 04:27, Denis Barbier a écrit :
On 2010/7/26 David Prévot wrote:
> Le 25/07/2010 18:41, Omar Campagne a écrit :
>> David, just shout if you want/need a hand with the unfuzzying of
>> the translated files (or sthg you can think of).
>
> Thanks a lot for the offer: I've quite finish to modify every style
> stuff the way I presented them earlier on this thread, and it appears to
> be a huge patch [...]
Please find attach the current patch, it contains mostly style stuff
like s/po/PO/ and s/docbook/DocBook/. As previously announced, it also
contains also some text shrunk from po4a-build.conf(5) (remarks about
how "po4a -k" were incorrect). finally, I didn't edit much things in
this manual, so I may not bother debian-l10n-english(a)l.d.o, for a review.
Anyway, I'm still ready to do so, because it seems to me that the use of
the "content" and "support" (and particularly "includes
support")
everywhere make this document a bit unclear (e.g. "po4a-build includes
support for adding gettext support for translation of script output
messages" or "support for Perl modules containing POD content"). I'm
ready to prepare a lighter version and propose it for review if you
still agree (not sure if people not subscribed to po4a-devel can post to
it, if not, people interested in the review process are welcome to say
so in order to be CCed).
> I'm not quite sure of what will be the best way to proceed
(in fact
> there is now way it could automatically be unfuzzied, except maybe for a
> tiny part of the strings, but it won't worth to separate them).
>
> I can think of two approach:
> - proceed one master file at a time: updating one of the master
> document, and unfuzzy the corresponding PO files;
> - apply the whole patch, and proceed one PO file at a time.
Please have a look at msguntypot, this may help a lot.
This was actually my initial idea, but on a second thought, I'm pretty
sure that style stuff like s/po/PO/ and s/docbook/DocBook/ would also
deserve to be applied on the translated string, and I doubt it can be
automatically done.
When English documentation is reviewed, it would be great to split
changes into two patchsets, the first one containing English fixes
with no semantic changes (for which no translation changes are
needed), and the second one containing semantic changes.
I would do so if it deserves it, but I think it will be quite useless to
bother separate a pair of strings just to make around 1% automatic (I
think around 98% of the strings could be manually unfuzzy be me or any
other volunteer before asking for translation update).
Unfortunately you will discover (like me ;)) that
lib/Locale/Po4a/Po.pm does not handle previous translations (flagged
with '#|'), they are removed in new files. I will try to fix that
tonight so that msguntypot from po4a 0.40 works as described above.
Thanks for your work anyway. I just discovered, while updating the
translation, the existence of msguntypot(1). It may be a better
alternative to the methods described in the developer's reference [0],
and could be announce there.
[0]
http://www.debian.org/doc/developers-reference/best-pkging-practices.html...
Cheers
David