bug-groff
[Top][All Lists]
Advanced

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

[bug #63808] configure gives incorrect information regarding pdf generat


From: G. Branden Robinson
Subject: [bug #63808] configure gives incorrect information regarding pdf generation
Date: Sat, 18 Feb 2023 17:29:11 -0500 (EST)

Update of bug #63808 (project groff):

                  Status:               Need Info => In Progress            

    _______________________________________________________

Follow-up Comment #32:

I think what this is is establishing is that the presence of the "gs" command
is a *bad* proxy for the presence of downloadable font file.

Distributors like Debian go out of their way to ensure that you can have that
executable on the system without the fonts being present.

And if the fonts are built into the executable--if I remember correctly, this
is the %rom% thing--then we don't have a good way of knowing whether this is
the case.  Not without writing a much more elaborate Autoconf test that really
uses Ghostscript to generate a PostScript document and then parses it,
perhaps.

Bertrand said he's available to tag RC3 tomorrow so what I think I will do is
internally modify check-default-foundry.sh to have two tests: one for the base
14+EURO and one for the rest.  The test will be skipped if the remainder are
missing.  Maybe that will be enough of a clue to check things out for the user
who goes to the trouble of running "make check" at all.

There's one more thing before I forget:


BuildFoundries: notice: copied grops font TR
BuildFoundries: GBR: LocateFile("ARRAY(0x55937cdc5598)", "ZCMI", 0)
BuildFoundries: GBR: LocateFile did not return early
BuildFoundries: GBR: LocateFile: checking directory
$p="/home/branden/BUILD/groff-1.23.0.rc2.87-206dc/font/devps"
BuildFoundries: GBR: LocateFile: checking file for pathfulness $file="ZCMI"
BuildFoundries: GBR: LocateFile: trying to read
$p/$file=/home/branden/BUILD/groff-1.23.0.rc2.87-206dc/font/devps/ZCMI
BuildFoundries: GBR: LocateFile: returning
$p/$file=/home/branden/BUILD/groff-1.23.0.rc2.87-206dc/font/devps/ZCMI
BuildFoundries: GBR: LoadFoundry: psfont="ZapfChancery-MediumItalic",
gropsfnt="/home/branden/BUILD/groff-1.23.0.rc2.87-206dc/font/devps/ZCMI"

BuildFoundries: GBR: LocatePF: looking for $path="ARRAY(0x55937cdc1cb8)",
$file="Z003-MediumItalic.t1!Z003-MediumItalic!URWChanceryL-MediItal!z003034l.pfb"
BuildFoundries: GBR: LocateFile("ARRAY(0x55937cdc1cb8)",
"Z003-MediumItalic.t1!Z003-MediumItalic!URWChanceryL-MediItal!z003034l.pfb",
0)
BuildFoundries: GBR: LocateFile did not return early
BuildFoundries: GBR: LocateFile: checking directory $p="@urwfontsdir@"
BuildFoundries: GBR: LocateFile: checking file for pathfulness
$file="z003034l.pfb"
BuildFoundries: GBR: LocateFile: trying to read
$p/$file=@urwfontsdir@/z003034l.pfb


"@urwfontsdir@" should not be getting left in the Foundry file as a literal. 
If its expansion is empty, it (and the path separator after it) should be
removed from the generated file.

I don't think this is a big deal, and certainly not release-critical.  But we
should tidy it up at some point.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?63808>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/




reply via email to

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