bug-groff
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Regressions in UTP document (was: removing the .IX macro from the ms


From: Deri
Subject: Re: Regressions in UTP document (was: removing the .IX macro from the ms package in 1.23 breaks old documents)
Date: Fri, 04 Oct 2024 16:41:19 +0100

On Friday, 4 October 2024 02:53:02 BST G. Branden Robinson wrote:

> Hi Deri,

>

Hi Branden,


> > The extra blank pages and the erroneous bookmarks are probably linked

> > and seem to be caused by commit

> > 5808f3f4dd8f39341170597363a6aaf7acf921fd, which was a fix to a

> > regression introduced into 1.23.0.

>

> Ah, you in fact already reported this.  (Thanks!)  And I thought I fixed

> it in 931da6d4d0 (5 June, this year.).  What's the status?  Does the fix

> not work?


The fix in June did fix the original problem with page breaks in the FBDL document that Michał was working on, but does not fix the problem with UTP.


As an aside, were you aware that FBDL has now moved away from groff and is using typst instead[1]. Must have been a lot of work to port to another system, I wonder if we should reach out to Michał and find out his reasons for changing. I did wind his git back to the point just before the switch to typst and ran with the current groff and received 1198 font errors which were not present in previous groff versions, I don't know if this had a bearing on his decision, but it must be annoying when the goalposts keep changing and new versions are incompatible with previous releases, particularly when there is no deprecation of previous "valid" roff to warn of an upcoming change, but bang into an error which affects the output.


I am certainly not against changes to groff, but I do think when we do alter groff in some way which will affect the typesetting of existing documents it is good manners to deprecate the change before making it an error which will alter the way the document appears.


Cheers


Deri


[1] https://github.com/typst/typst


reply via email to

[Prev in Thread] Current Thread [Next in Thread]