po4a-Bugs item #315075 was changed at 05.01.2017 01:04 by Alexander Golubev You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=31... Status: Open Priority: 3 Submitted By: Luiz Fernando Rangheti (elchevive-guest) Assigned to: Nobody (None) Summary: po4a 0.46 breaks formatting of man pages Category: None Group: None Resolution: None Initial Comment: Hi, I package po4a for openSUSE and in the last update, 0.46 it breaks the formatting of man pages. You can see more information on the comments here: https://build.opensuse.org/request/show/308224 Regards, Lui ---------------------------------------------------------------------- Comment By: Alexander Golubev (fat-zer-guest) Date: 05.01.2017 01:04 Message: http://git.savannah.gnu.org/cgit/man-db.git/commit/?id=f8034f54218d002d35... ---------------------------------------------------------------------- Comment By: Luiz Fernando Rangheti (elchevive-guest) Date: 20.09.2016 12:49 Message: Any progress? I'd like to update po4a in openSUSE to 0.48 but I'm stuck with 0.45 ---------------------------------------------------------------------- Comment By: Martin Quinson (mquinson) Date: 29.06.2015 23:39 Message: @Robert: Any progress on this maybe? I'm myself not very confident with the Man module and your help is really welcome. Also, do you know why man-db is using its own module? Should we try to merge our efforts maybe? Many many thanks for your help. ---------------------------------------------------------------------- Comment By: Robert Luberda (robert) Date: 31.05.2015 23:41 Message: My initial patch handles only '\t' as column separator, while man-db package uses '@'. I am working on a fix for this. However man-db package uses its own Manext.pm module which implements handling of textblocks in its own way, and I am afraid that this man-db's module will need to be changed as well. ---------------------------------------------------------------------- Comment By: Alexander Golubev (fat-zer-guest) Date: 25.05.2015 12:59 Message: I can confirm it on gentoo. And that the bug was introduced with the release. Compare: === mandb.8.original === .TS tab (@); l l l l. Name@Type@Async@Filename _ Berkeley db@T{ Binary tree T}@Yes(a)\fIindex.bt\fR GNU gdbm v >= 1.6@T{ Hashed T}@Yes(a)\fIindex.db\fR GNU gdbm v < 1.6@T{ Hashed T}@No(a)\fIindex.db\fR UNIX ndbm@T{ Hashed T}@No(a)\fIindex.(dir|pag)\fR .TE === mandb.8.ru [0.45] === .TS tab (@); l l l l. Название@Тип@Асинхронность@Имя файла _ Berkeley db@T{ двоичное дерево T}@Да(a)\fIindex.bt\fP GNU gdbm v >= 1.6@T{ Хэш T}@Да(a)\fIindex.db\fP GNU gdbm v < 1.6@T{ Хэш T}@Нет(a)\fIindex.db\fP UNIX ndbm@T{ Хэш T}@Нет(a)\fIindex.(dir|pag)\fP .TE === mandb.8.ru [0.46] === .TS tab (@); l l l l. Название Тип Асинхронность Filename _ Berkeley db T{ двоичное дерево T} Да \fIindex.bt\fP GNU gdbm v >= 1.6 T{ Хэш T} Да \fIindex.db\fP GNU gdbm v < 1.6 T{ Хэш T} Нет \fIindex.db\fP UNIX ndbm T{ Хэш T} Нет \fIindex.(dir|pag)\fP .TE ---------------------------------------------------------------------- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=31...