On Fri, May 22, 2015 at 05:14:20PM -0400, David Prévot wrote:
Hi Martin,
On Fri, May 22, 2015 at 10:39:33PM +0200, Martin Quinson wrote:
You could even raise the gravity of that bug to block the package transition to testing if you feel that this change should be reverted.
Even if disruptive changes in the gettext/po4a toolchain (and underlined Perl handling) are always painful (one has to make sure every contributor is using the “right” version, the amount of changes in the PO files to cope with the upgrade can be huge), with my Debian packager hat on, I’d say that now (early in the development cycle) is exactly the right moment to make such change if it’s an improvement worthing the disruption.
I completely missed the point that such a change would be very disruptive and thus not desirable when facing large text corpus. Sorry. Again, I'll try to launch the build of manpages-fr to check my changes before uploading. Not sure that I will manage to notice such massive fuzzing, but I will try.
About this change, now. My current feeling is that it should be an optional behavior. It is very possible to pass options to the PO4A modules, so that users may choose how to handle tbl macros. David, do you think that it would do the trick?
If so, I will do so in the next week (I'm currently out of town), but if someone manages to prepare a patch before me, I'd be really thankful.
Bye, Mt.