Red Hat Bugzilla – Bug 142294
a2ps default configuration is lacking
Last modified: 2007-11-30 17:10:56 EST
Description of problem:
In a default /etc/ap2s.cfg for "AppendLibraryPath" one can see:
which is not really right in the context. As a result
'a2ps --list-options' produces:
library path =
and '/usr/share/a2ps/afm/make_fonts_map.sh' does not see many
useful fonts which most likely are on the system.
Here is a list of various directories found with .afm files
(that is what a2ps is looking for):
Even after dropping "yandy" from that list, and possibly few
others, this still leaves quite a number which look much more
useful than /usr/local/ghostscript/fonts.
Version-Release number of selected component (if applicable):
I am not sure about that but it seems that metrics only may be not
good enough and a2ps makes a tacit assumption that a font file will
be found in the same directory as its metric - which may or may not
be true. Last night I rewrote myself make_fonts_map.sh script to
add a font to a map file only if both some_name.afm and
some_name.pf[abm] are found somewhere in a declared path (with an
exception of a2ps directories on a hope that a2ps knows what it is
doing; which may be too optimistic). Are you interested?
Metrics only should be good enough in a case of "standard fonts".
These will be provided by Postscript printers and for other
ghostscript will make a substitution as needed.
I've really no idea about how that stuff works or is meant to work. :-(
Well, at least
in a default configuration should give a better "standard" layout.
(changing to devel since FC3 has a2ps-4.13b-41 and has the correct paths listed.)
Problem was that the a2ps-4.13-conf.patch only touched configure but not
Yes, this was about "devel". I listed a correct version but
failed to notice in bugzilla that not that branch was showing up.
OTOH my version of make_fonts_map.sh for some reasons finds on
FC3 installation, and without touching anything in /etc/a2ps.cfg,
thirty five more fonts than what shows up in a provided