summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/source/fonts/pclnfss/README
blob: 1e9a1cb877965bcb067c1c46e8f254aff123bf2c (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
These files were used with fontinst 1.317 to create the VF/TFM files for
the HP builtin font in TeX-compatible encodings.

The GNUmakefile is probably of no use as-is to anyone but me; it depends
on lots of my development pathnames, etc.

{0n,10u,2n,6j,7j,8u,9t}.etx are encoding files I made up for the HP
encodings that I used. I chose which encodings to use based on (all
other factors being equal) how many fonts had that encoding available.
There are many other HP encodings. Norm (Walsh) created the builtin
fonts in all of them, and you can use them directly if you wish.

*.etw are bits of encoding files that are repeated in all the encodings.

*.map and k2n.awk are used by the GNUmakefile to go from Norm's names to mine.

etxmac.tex, fontdim.tex, fonthp.tex, and uclc.tex are utility TeX macros
used to make the encoding files shorter and avoid duplication.

fontinst.rc defines \HEADER (to do nothing), since our fonts have extra
headerbyte info.  This will presumably appear in fontinst proper at some
point.

hptex.tex could be read by (plain) TeX documents to take advantage of
the extra characters in the plain-compatible encoding.

latin.mtx is the usual fontinst one minus the smallcap definitions. I
found that my (big) TeX ran out of memory with the smallcap definitions,
and my encodings don't use them, so ...

oneline.tex creates a document with one-line showings of all the builtin
fonts. You'll need to apply the following patch to dvicopy to process
the resulting dvi files.

rmligdups.awk is necessary because we have (much) duplicate kerning info
in our fonts. Given two entries for a kerning pair (X,Y) fontinst writes
them both, instead of just the latter. The result is a VPL file that's
too big for vptovf (and maybe too big for the TFM/VF formats at all, I forget).

test.tex uses testfont.tex routines to exercise the fonts.

--kb@cs.umb,edu, 25feb94

Change dvicopy.ch to this if you want to. This suffices to expand oneline.dvi.
(ftp.cs.umb.edu:pub/tex/web2c.tar.gz)

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% [5] Make name_length match the system constant.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
@x
@<Constants...@>=
@!max_fonts=100; {maximum number of distinct fonts}
@!max_chars=10000; {maximum number of different characters among all fonts}
@!max_widths=3000; {maximum number of different characters widths}
@!max_packets=5000; {maximum number of different characters packets;
  must be less than 65536}
@!max_bytes=30000; {maximum number of bytes for characters packets}
@!max_recursion=10; {\.{VF} files shouldn't recurse beyond this level}
@!stack_size=100; {\.{DVI} files shouldn't |push| beyond this depth}
@!terminal_line_length=150; {maximum number of characters input in a single
  line of input from the terminal}
@!name_length=50; {a file name shouldn't be longer than this}
@y
@d name_length==PATH_MAX

@<Constants...@>=
@!max_fonts=300; {maximum number of distinct fonts}
@!max_chars=750000; {maximum number of different characters among all fonts}
@!max_widths=10000; {maximum number of different characters widths}
@!max_packets=20000; {maximum number of different characters packets;
  must be less than 65536}
@!max_bytes=100000; {maximum number of bytes for characters packets}
@!max_recursion=10; {\.{VF} files shouldn't recurse beyond this level}
@!stack_size=100; {\.{DVI} files shouldn't |push| beyond this depth}
@!terminal_line_length=256; {maximum number of characters input in a single
  line of input from the terminal}
@z