From 72d22e8a1a1b47635e1b8da49ae703bde01228f2 Mon Sep 17 00:00:00 2001 From: Ben Harris Date: Sat, 27 Jan 2007 20:47:41 +0000 Subject: Add support for PFB files. This seems to have caused me to completely rewrite the Type 1 font support, and I'm sure the result is more complex than it needs to be, but it seems to work correctly, so I shouldn't complain. [originally from svn r7175] --- doc/output.but | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) (limited to 'doc') diff --git a/doc/output.but b/doc/output.but index df4580e..001a03a 100644 --- a/doc/output.but +++ b/doc/output.but @@ -1673,14 +1673,15 @@ built into all PDF and most PostScript implementations. These are: \b \cw{Courier-BoldOblique} -These fonts can be used without further formality. To use any other font, -Halibut needs at least to know its measurements, which are provided in an -\i{Adobe Font Metrics} (\I{AFM files}AFM) file. Halibut can also -\I{embedding fonts}embed -\i{Type 1 fonts} in its PDF and PostScript output if provided with an -ASCII-format (\I{PFA files}PFA) font file. To provide an AFM or PFA file -to Halibut, simply name it on Halibut's command line. If both are named, -the AFM file must come first. +These fonts can be used without further formality. To use any other +font, Halibut needs at least to know its measurements, which are +provided in an \i{Adobe Font Metrics} (\I{AFM files}AFM) file. +Halibut can also \I{embedding fonts}embed \i{Type 1 fonts} in its PDF +and PostScript output if provided with font file in either hexadecimal (\I{PFA +files}PFA) or IBM PC (\I{PFB files}PFB) format. To provide +an AFM, PFA, or PFB file to Halibut, simply name it on Halibut's command +line. If a PFA or PFB file is specified, the corresponding AFM file +must come first. \ii{Font sizes} are specified in PostScript \i{points} (72 to the inch). -- cgit v1.1