On 9/03/2026 4:51 pm, Stuart Henderson wrote:
On 2026/03/09 15:07, Larry Moore wrote:
I'm working through the issue with the Ghostscript fonts and have
the faxsetup script working.
The remaining problem is that the fonts generated and listed in the
Fontmap.HylaFAX file (generated using HylaFAX+ genfontmap.ps), is
that the fonts listed cannot be found on the system.
It appears the fonts required would normally be in
${LOCALBASE}/share/ghostscript/${VERSION}/Resource/Font.
Looking through changes in CVSWEB, I haven't found any comments
relating to the Resource folder, let alone why it was removed. It
appears they disappeared from the build on the 27th of January 2022
- see
https://cvsweb.openbsd.org/checkout/ports/print/ghostscript/gnu/pkg/PLIST,v?rev=1.30
Would someone be able to explain why this change was made?
Upstream changed default builds to use compiled-in fonts (they call it
a rom-based filesystem, search for %rom% in ghostscript source to find
code related to this). Not sure exactly when it was done, current docs
suggest it can be disabled but don't say how:
https://ghostscript.readthedocs.io/en/latest/Use.html#explicit-cidfont-substitution
Thanks Stuart.
Looking at point 4 in
https://ghostscript.readthedocs.io/en/latest/Use.html#testing-a-file-name-for-an-absolute-path
COMPILE_INITS appears it can be set to 0 using the configure switch
--disable-compile-inits.
The real issue at the moment is the generated FontMap file in HlyaFAX
lists the fonts using the newer naming convention.
The textfmt(1) program doesn't call ghostscript when generating its
PostScript file. It is looking for external AFM's to use. The extarn AFM
fonts are installed with ghostscript-fonts-8.11p3. These fonts use the
older naming convention, hence the faxsetup(8c) script doesn't match the
font name when searching the AFM files.
For now, it may be simpler to script the generation of a fontmap file by
using the the fonts.dir file, which is installed with
ghostscript-fonts-8.11p3. This is my next approach to test.
Cheers,
Larry.
