On Wed, Jan 07, 2009 at 07:25:02PM +0100, Agustin Martin wrote: > On Sun, Jun 02, 1996 at 02:26:00AM +0100, Ian Jackson wrote: > > Package: linuxdoc-sgml > > Version: 1.5-2 > ... > > To debian-devel and the package maintainer: I think that most of > > these problems are upstream ones; some may require considerable > > effort to fix, so I'm causing the bug system to CC the linuxdoc-sgml > > mailing list. Hi, Ian > Mailing you about this really ancient bug report, so we get your feedback > about what to do. ... > As mentioned above, I do not intend to make deep changes in the package, > besides fixing bugs when possible and rewritting/reorganizing things in a > way I like more, so I only intend to have this package in a minimally > reasonable shape. ... > > (d) The filename heading before the first node lists a file in /tmp. > > I don't know if this is fixable, but it would be nice if it said > > that the thing came originally from programmer.sgml or whatever. > > Output file can be postprocessed to change this info. Unfortunately makeinfo > is too rigid to do this when first creating the info file. Not sure if this > worths, but is something I do not discard.
I first modified this in 0.9.65 and added an additional fix in 0.9.66. ... > > (h) The existence of a paragraph break after <descrip> entries is > > unpredictable. > > At the first look seemed that groff gets confused about consecutive multiple > <p> and empty lines. After a deeper look, my guess is that this is a > page-break related problem, seems that with current code groff is breaking > pages in a supposedly continuous text output, ans things are joined in a > page-break. > > The workaround is to play with the numbers of <p> or empty line. Really > suboptimal. I wish I could tell groff that this is a continuous text. I am testing a way to make groff consider the document as a large single page, based in http://lists.gnu.org/archive/html/groff/2011-02/msg00020.html http://www.groff-wiki.info/EmittingOnePage This seems to work and will go in next upload. Since these were the last things from your original exhaustive bug report that I was considering to deal with, I plan to close this historical bug report with that upload. Regards, -- Agustin -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
