Re: [Po4a-devel] Unfuzzying and docs corrections.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Le 25/07/2010 18:41, Omar Campagne a écrit : 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 (~90KB already, at least the documentation is not yet translated in as much languages than the runtime strings)... 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. In any case, it will probably need to be carefully tested, using a diff between the VCS version and the updated one (I did it recently for the developers-reference and the maint-guide: it is possible to quickly spot what are the new fuzzy string by looking for the "+#, fuzzy" pattern in the diff which can easily be updated). Maybe the second approach could be better to split the work: once the diff applied to every master documents, everyone can construct the new PO files and unfuzzy the strings with the method of his or her choice (since the Spanish is up to date, I would appreciate if you could at least take care of this one), if you have a better method than mine, don't hesitate to share it neither ;-). Anyway, I plan to propose a review on debian-l10n-english(a)l.d.o, for at least po4a-build.conf(5), so I guess the unfuzzing work could begin once this review is done, and the other parts of the patch accepted: probably in two weeks, maybe ten days if we want to make it quick (I guess it's a reasonable minimum amount of time, hopefully there will be no more translations on their way at this moment). I fully agree, and translated documentations are possible thanks to po4a, that's also why I'm interested to help and make its documentation as good as I can. Cheers David