[Top][All Lists]

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

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

From: Deri James
Subject: [bug #63808] configure gives incorrect information regarding pdf generation
Date: Fri, 17 Feb 2023 08:19:32 -0500 (EST)

Follow-up Comment #17, bug #63808 (project groff):

I am glad you have said that, starting to run out of hair!

To be clear the major problem occurs when configure is run and it finds the
URW fonts but not ghostscript, a minor problem is the check tests.

First some definitions:-

Standard gropdf

This is when only the default foundry is populated with the 35 postscript
fonts. This will occur if only ghostscript is available. PDF documentation
will be complete. The font test should look for all the 35 fonts, error if any
are missing.

Enhanced gropdf

Both the default and the U- foundry are populated. This will occur if the URW
fonts are available. PDF documentation will be complete. In addition to the
font test for standard gropdf also check for the same 35 but starting with

Restricted gropdf

Only the base-14 fonts are available in the default foundry, there is no U-
foundry. This will occur if neither ghostscript nor URW fonts are found. PDF
documentation (if run will be "restricted", see below. It is not worth doing
any font checks, the base-14 fonts are always populated by BuildFoundries.

Restricted PDF documentation

This is documentation produced if only the base-14 fonts are available. You
will notice warnings from throff about not finding particular fonts, and
warning from gropdf about not being able to embed fonts (if gropdf has been
called with -P-e). A "valid" pdf will be produced (i.e. it can be opened with
a viewer), but the fonts used in the pdf will be sub-optimal! When fonts can't
be selected by troff it continues with the previous valid font. I'm not sure
if this is "good enough" for the pdf documentation - your call.

Confusion over basic-fonts-present.sh

This used to check all the fonts in the default foundry were present - good.
It could be used for the Standard Gropdf test. Then in comment #9 you received
a number of missing fonts for a ghostscript only run and the check failed.
This is absolutely correct, for a ghostscript only run all the default foundry
fonts should be present, good the check worked. Why did you then change the
code to make it pass the test, rather than investigate why you ended up with a
restricted gropdf when a standard gropdf should be expected. The check, as it
currently stands,  is meaningless, the result of running BuildFoundries will
always produce at least the base-14 fonts, which is what you are now checking,
it can never fail, so is a bit pointless. If you can reproduce this results -
a restricted gropdf after a run with ghostscript available - please post the
configure and run logs. If you can't please can basic-fonts-present.sh be
returned to its former glory.


Reply to this item at:


Message sent via Savannah

reply via email to

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