- How can I use ibmpc's line drawing characters?
First, you will need a PostScript font (.pfa or .pfb) which has
those line drawing characters. This is the trickiest task
since these fonts are really rare. Once you find one, you must
make it available for enscript (see file README for details) so
it can be downloaded to the printer.
Since these suitable fonts are so rare, the ibmpc encoding do not
contain mappings for those line drawing characters, this means they
won't print if you use the ibmpc encoding. You must rely on the
font's build-in encoding and print your files with option `-X ps' or
`--encoding=ps'.
- How can I use the ISO-8859-7 input encoding?
Manolis Lourakis
(lourakis@csd.uch.gr)
has written a document that describes how this can be done. It
can be found from URL:
http://www.csd.uch.gr/~lourakis/genscript/
- I tried the iso8859/2 input encoding but enscript says that 44
characters were missing and I get '?' on paper instead of latin2
characters. Did I missed something? (This answer holds also for
other input encodings).
No, everything is ok but the problem is that Adobe's default Courier
font does not have characters named: Aogonek, Lcaron, Sacute, Tcaron,
Zacute, ... (those 44 missing characters) so enscript can't print
them. You can solve this if you have a courier (or whatever) font
that has those missing characters. One good canditate is courier
font distributed with the X distribution, it is called cour.pf{a,b}
and should be found from all good FTP sites.
To solve this problem, you must:
- find a nice font to do the job.
- copy this font and its AFM file to some appropriate directory,
let's say `$HOME/fonts/':
$ ls fonts/cour*
fonts/cour.afm fonts/cour.pfa
- create a font map for this new font directory (mkafmmap
program comes with the enscript distribution):
$ cd fonts
$ mkafmmap *.afm
file=font.map
BrushScript.afm...
Hobo.afm...
Stencil.afm...
cour.afm...
uaqrrc.afm...
ugqb.afm...
unmr.afm...
unmrs.afm...
- edit enscript's personal (or the global) configuration file to
use this new font:
$ cat ~/.enscriptrc
#
# My enscript init file.
#
DefaultFancyHeader: emacs
#PageLabelFormat: long
Clean7Bit: 0
AFMPath: /home/mtr/fonts:/usr/local/share/enscript
- now it should work:
$ cd myprogs/enscript/
$ enscript -v -G2r -pfoo.ps latin2.txt
AFM: scanning path...
AFM: reading font map "/home/mtr/fonts/font.map"
AFM: reading font map "/usr/local/share/enscript/font.map"
reading AFM info for font "Courier"
processing file "latin2.txt"...
[ 3 pages * 1 copy ] left in foo.ps
Now enscript uses this new courier font that has those missing
characters. Since the font file `.pfa' is found from the font
path, enscript automatically includes that font file to your
PostScript output. This means that it can be printed with any
PostScript printer; now file really contains that font so it does
not depend on printer's fonts.