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
78
|
Viewing and Editing truetype instructions in FontForge.
=======================================================
.. image:: /images/ttfinstrs-view.png
.. image:: /images/ttfinstrs-edit.png
* `Apple's overview on instructing glyphs <http://developer.apple.com/fonts/TTRefMan/RM03/Chap3.html>`__
* `Apple's list of truetype instructions <http://developer.apple.com/fonts/TTRefMan/RM05/Chap5.html>`__
* `Apple's description of the truetype graphics state <http://developer.apple.com/fonts/TTRefMan/RM04/Chap4.html>`__
* `Apple's summary of truetype instructions <http://developer.apple.com/fonts/TTRefMan/RM07/appendixA.html>`__
I shall not attempt to describe the mechanics of instructing truetype, if you
want to understand it I refer you to the above links.
(`Microsoft has a similar set <http://www.microsoft.com/typography/OTSPEC/ttinst.htm>`__
in but they are in word format).
This dialog shows the instructions associated with a glyph or truetype table
(like fpgm or prep). If you move your mouse cursor over one of the instructions
a brief help message will pop up describing that instruction. If you press the
[Edit] button the dlg will change and you will be presented with a editable
textarea containing the same instructions. You may modify these to your heart's
content. Pressing the [Parse] will parse your modifications and (if they parse)
return you to the "help" mode.
Instructions like MIRP may be entered either in FontForge's peculiar (but
marginally more mnemonic) style: ``MIRP[rnd,white]`` or as ``MIRP[00110]``, and
``PUSHB_1`` may be ``PUSHB[000]``.
You may also include an stack arguments on the same line as the instruction and
FontForge will convert them into the appropriate pushes. So...
::
5 SRP0
is equivalent to
::
PUSHB_1
5
SRP0
You may also use the expression ``cvt(<val>)`` instead of a number. This will be
replaced by the index in the 'cvt ' table of an entry which is (within one
em-unit of) <val>. So ``cvt(100)`` would return the index in 'cvt ' of 100. If
there is no such entry, FontForge will create one.
When editing DELTA* instructions you might want to use the syntax:
::
PUSHB_3 6@12 8 1 DELTAP2
This means: Move point 8 by six delta-steps at 37 ppem (that's not clear at
first glance - assuming delta_base is 9, DELTAP2 works from 25 ppem to 25+15
ppem, in this example it's 25+12 ppem). So it's just a way of constructing an
argument byte for DELTAP/C.
.. _ttfinstrs.cvt:
Editing the 'cvt ' table directly
---------------------------------
.. image:: /images/editcvt.png
:align: right
This dialog shows the initial contents of the 'cvt ' table (before it has been
modified by the 'prep' program). It is simply a list of signed 16bit values. You
may change any value by clicking on it and typing a new value. You may also
attach comments to entries, this can be helpful in reminding yourself what this
index is used for. You may add new entries (at the end) with the [Change Length]
button.
(You may also use the "``cvt(<val>)``" notation described above to add entries
to the cvt table without using this dialog.)
|
