nasm/doc
H. Peter Anvin 18e87ce7bd doc: we really need a Fontmap file
It turns out that we need a Fontmap file after all, *and* -I. to make
gs find it. Inconsistent results came from stray Fontmap files from
previous debug attempts.

Now generate both fontpath and Fontmap, and hopefully at least one of
them should work. We might, in fact, need both, one for gs to know
where the files are and one for gs to know it is allowed to read them.

The core problem seems to be that gs will find OTF fonts by its normal
discovery mechanisms, but for some reason don't seem to use them
unless it can find them in a Fontmap, Font directory, of CIDFont
directory.

Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2019-10-04 13:09:30 -07:00
..
afmmetrics.ph
changes.src
findfont.ph doc: fix yet another set of Ghostscript font problems 2019-06-06 20:51:10 -07:00
genps.pl doc: we really need a Fontmap file 2019-10-04 13:09:30 -07:00
head.ps
inslist.pl
internal.doc
local.css
Makefile.in doc: we really need a Fontmap file 2019-10-04 13:09:30 -07:00
nasmdoc.css
nasmdoc.src Correct __ALIGN_ -> __?ALIGN_ 2019-08-27 17:21:28 -07:00
nasmlogo.eps
nasmlogw.png
opt_var.txt
psfonts.ph
pspdf.pl doc: we really need a Fontmap file 2019-10-04 13:09:30 -07:00
pswidth.ph
rdsrc.pl
README
ttfmetrics.ph

To build the entire documentation, the following tools are needed:

1. A Perl interpreter for your platform
2. The following Perl modules available from CPAN:
   Font::TTF
   Sort::Versions
3. asciidoc
   http://asciidoc.org/
4. xmlto
   https://fedorahosted.org/xmlto
5. One of:
	Adobe Acrobat (acrodist)
	Ghostscript (ps2pdf) http://download.ghostscript.com/
	pstopdf	(available on some BSD-derived Unix systems)

	Of these, Ghostscript is the most tested, although Acrobat has
	been claimed to generate smaller files.
6. For best results, the Adobe fonts Source Sans Pro and Source Code
   Pro, available for free at:
   https://github.com/adobe-fonts