On Sunday, 15 December 2024 20:03:50 GMT G. Branden Robinson wrote: > At 2024-12-15T16:22:59+0000, Deri wrote: > > It looks like it is a regression (from 1.23.0) because if I remove the > > "kludge" and change the GNU png to pdf (so it is compatible with > > running 1.23.0) it works in 1.23.0 but is wrong in current. I also > > tested using 1.23.0 groff and run the output through current gropdf > > and the result was good. > > I'm not able to reproduce this problem in my working copy--the GNU head > shows up, if fuzzily--and I haven't frotzed around in the formatter > since I last pushed.
Hi Branden, Fuzzilly is to be expected - it is only 25x22 pixels. I thought Peter's question was why did he need to add a kludge (a white period) to make it work? I confirmed the kludge was not required using 1.23.0. Unfortunately, your test script (which works just as well as Peter's original) does not show the problem because it includes the kludge!!! [...] > Attaching my results. I modified the exhibit to force the formatter to > disclose full version information (this requires the `-U` option). > Also, since I stored the artifacts in my "EXPERIMENTS" directory, it > expects to find the GNU head image there. I have attached a version (sans kludge) which you can use for your testing, along with a pdf showing what output without the kludge looks like. Please note I have changed the png to a pdf, since 1.23.0 only accepted images as pdfs, so it means you can use the same code for both groff versions. > Regards, > Branden Please confirm you can now see the regression, I ask because I don't quite understand why, when I wrote this:- "if I remove the "kludge" and change the GNU png to pdf (so it is compatible with running 1.23.0) it works in 1.23.0 but is wrong in current." you tested with a version of the script which included the kludge and used a png so would not be able to run on 1.23.0!! You do like to make me type a lot. :-) Cheers Deri PS You may notice I am one commit in front of you, this is because I get an error running bootstrap (after distclean) unless I add & commit gnulib beforehand (I then git reset HEAD~ after bootstrap because its not my code so I don't want to include it the next time I push origin master). Is there any way I can avoid this rigmarole? This is what it wants me to commit:- diff --git a/gnulib b/gnulib index b28dc133f..39d328338 160000 --- a/gnulib +++ b/gnulib @@ -1 +1 @@ -Subproject commit b28dc133f6e7f6536ed35acbccb28eeb8355fc49 +Subproject commit 39d328338895f4fd219eb7dcf2cc652daf4e1fdd And this is the error from bootstrap if I don't go through the commit/reset cycle:- fatal: remote error: upload-pack: not our ref b28dc133f6e7f6536ed35acbccb28eeb8355fc49 fatal: Fetched in submodule path 'gnulib', but it did not contain b28dc133f6e7f6536ed35acbccb28eeb 8355fc49. Direct fetching of that commit failed.
problem-gnu-head.pdf
Description: Adobe PDF document
.\" pdfmom -U .\" Build with pdfmom(1); output to pdf . .sp 6P-1v . .nr img-w 25p .nr img-d 22p . .di img-div .ev img-div .nf \X'pdf: pdfpic EXPERIMENTS/GNU-head-small.pdf' .ev .di . .char \[img] \*[img-div] .ds gnu \v'-\n[img-d]u'\[img]\h'\n[img-w]u' . .nop A GNU head \*[gnu] image. . .sp .pso troff --version
GNU-head-small.pdf
Description: Adobe PDF document