There appear to be two bugs in how gropdf (from 1.23.0) writes the
CreationDate/ModDate. To demonstrate I am running
while sleep 60; do date; echo "" |
groff -Z -Tpdf | gropdf | fgrep -a Date; done
which results in the following output:
Thu 4 Apr 23:30:55 CEST 2024
5 0 obj << /CreationDat
On Thu, Apr 04, 2024 at 06:21:37PM -0500, G. Branden Robinson wrote:
> Hi Christof,
>
> Thanks for the report.
>
> At 2024-04-04T23:44:25+0200, Christof Meerwald wrote:
> > There appear to be two bugs in how gropdf (from 1.23.0) writes the
> > CreationDate/ModDate.
Hi,
just gave 1.23.0.rc3 a quick try and noticed a difference for the
following input with -ms (-Tascii and -Tpdf show the same difference):
.nr PD 1v
.LP
X1
.LD
X2
.DE
.LP
X3
.LD
X4
.DE
X5
.LP
.LP
X6
with 1.23.0.rc3 I now only get a single blank line between X2 and X3,
but with earlier versions
On Sun, Apr 09, 2023 at 02:11:17PM -0500, G. Branden Robinson wrote:
> At 2023-04-08T19:38:49-0500, G. Branden Robinson wrote:
> > Yes. Technically, this changed behavior is the result of a bug fix to
> > bring our rendering of ms documents more in line with AT&T troff ms, and
> > we don't ordinar
Unfortunately, previously reported vertical spacing regression for ms
macro package is still present in 1.23.0.rc4.
For the document:
.nr PS 12p
.nr DD 0p
.LP
A \n[nl]
.NH
B \n[nl]
.EQ
C \n[nl]
.EN
.NH
D \n[nl]
.LP
E \n[nl]
.DS
F \n[nl]
.DE
.NH
G \n[nl]
.LP
H \n[nl]
formatted with "groff -Tpdf -
On Thu, Apr 20, 2023 at 03:00:45PM -0500, G. Branden Robinson wrote:
> 2. addressed in documentation on master (NEWS) prior to RC4
>(f9e84954174); reporter remains unhappy, but does not respond to
>requests for more precise information
I guess the technical details should be well understoo
