Bug#786525: Disruptive changes should be loudly announced

2015-06-24 Thread Martin Quinson
Hello, On Sat, May 23, 2015 at 10:34:30PM +0200, Martin Quinson wrote: On Fri, May 22, 2015 at 05:14:20PM -0400, David Prévot wrote: Even if disruptive changes in the gettext/po4a toolchain (and underlined Perl handling) are always painful (one has to make sure every contributor is

Bug#786525: Disruptive changes should be loudly announced

2015-06-24 Thread David Prévot
Hi Martin, Le 24/06/2015 16:40, Martin Quinson a écrit : On Sat, May 23, 2015 at 10:34:30PM +0200, Martin Quinson wrote: On Fri, May 22, 2015 at 05:14:20PM -0400, David Prévot wrote: Even if disruptive changes in the gettext/po4a toolchain (and underlined Perl handling) are always painful

Bug#786525: Disruptive changes should be loudly announced

2015-05-23 Thread David Prévot
Hi Martin, 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? Sure, making this new tbl handling

Bug#786525: Disruptive changes should be loudly announced

2015-05-23 Thread Martin Quinson
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

Bug#786525: Disruptive changes should be loudly announced

2015-05-22 Thread David Prévot
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

Bug#786525: Disruptive changes should be loudly announced

2015-05-22 Thread Martin Quinson
Damn, I'm stupid. I tested those changes in my own project, which uses html only and not the man pages. I knew that tbl is in that module... I'm sorry, I'll dig into it. You could even raise the gravity of that bug to block the package transition to testing if you feel that this change should be

Bug#786525: Disruptive changes should be loudly announced

2015-05-22 Thread David Prévot
On Fri, May 22, 2015 at 05:14:20PM -0400, David Prévot wrote: I hope the “convert a pre-existing translation to po4a” HOWTO from po4a(7) will ease the PO files changes needed to cope with the new way to handle man pages table (I intend to give it a try soon for procps and findutils, unless

Bug#786525: Disruptive changes should be loudly announced

2015-05-22 Thread David Prévot
Package: po4a Version: 0.46-1 Severity: normal Hi, I just spent a fair amount of time searching what did I do wrong while updating some manpages-fr-extra PO files, and finally figured out that the “Man module splits tbl's textblocks into separate lines” change in po4a was likely the cause of the