Hagen - Pragma ADE

More documents

Recommendations

Info

$Integrating TEX, MetaPost, JavaScript and PDF - Pragma ADE$

132 Extensions \definefontfeature [dimensions-c] [default] [dimensions={1,3,2}] \definefontfeature [dimensions-d] [default] [dimensions={3,3,3}] As usual you apply such a feature as follows: \definefont[MyFont][Serif*dimensions-a sa 2] In figure 8.6 you see these four definitions in action. The leftmost rendering is the default rendering. The three numbers in the definitions represent the width (in em), height and depth (in ex). g g g g g default 1em 1ex 1ex 1em 2ex 3ex 1em 3ex 2ex 3em 3ex 3ex Figure 8.6 Freezing dimensions of glyphs. This feature only makes sense for fonts that need a fixed width, like the cjk fonts that are used for asian scripts. Normally those fonts already have fixed dimensions, but this feature can be used to fix problematic fonts or add some more space. However, for such large fonts this also brings a larger memory footprint. 8.7 Unicoding Nowadays we will mostly use fonts that ship with a Unicode aware encoding. And in ConT E Xt, even if we use a Type1 font, it gets mapped onto Unicode. However, there are some exceptions, for instance the Zapf Dingbats in Type1 format. These have a rather obscure private encoding and the glyph names run from a1 upto a206 and have no relation to what the glyph represents. In the case of Dingbats we’re somewhat lucky that they ended up in Unicode, so we can relocate the glyphs to match their rightful place. This is done by means of a goodies file. We already discussed this in section 5.4 so we only repeat the usage. \definefontfeature [dingbats] [mode=base,
goodies=dingbats, unicoding=yes] \definefontsynonym [ZapfDingbats] [file:uzdr.afm] [features=dingbats] I tend to qualify the Dingbat font in T E X distributions as rather unstable because of name changes and them either or not being included. Therefore it’s best to use the hard coded name because that triggers the most visible error message when the font is not found. A font like this can for instance be used with the glyph placement macros as is demonstrated below. In the last line we see that a direct utf input also works out well. \getglyphdirect{ZapfDingbats*dingbats}{\number"2701} ✁ \getglyphdirect{ZapfDingbats*dingbats}{\char"2701} ✁ \getnamedglyphdirect{ZapfDingbats*dingbats}{a1} ✁ \getnamedglyphdirect{ZapfDingbats*dingbats}{a11} ☛ \getglyphdirect{ZapfDingbats}{\number"2701} unknown \getglyphdirect{ZapfDingbats}{\char"2701} unknown \getnamedglyphdirect{ZapfDingbats}{a1} ✁ \getnamedglyphdirect{ZapfDingbats}{a11} ☛ \definedfont[ZapfDingbats*dingbats]✁ ✁ Keep in mind that fonts like Dejavu (that we use here as document font) already has these characters which is why it shows up in the verbose part of the table. 8.8 Protrusion Protrusion is a feature that LuaTEX inherits from pdfTEX. It is sometimes referred to as hanging punctuation but in our case any character qualifies. Also, hanging is not frozen but can be tuned in detail. Currently the engine defines protrusion in terms of the emwidth which is unfortunate and likely to change. 11 It is sometimes believed that protrusion improves for instance narrower columns, but I’m pretty sure that this is not the case. It is true that it is taken into account when breaking a paragraph into lines, and that we then have a little bit more width available, but at the same time it is an extra constraint: if we protrude we have to do it for each line (and the whole main body of text) so it’s just a different solution space. The main reason for applying this feature is not that the lines look better or that we get better looking narrow lines but that the right and left margins look nicer. Personally I don’t like half protrusion of punctuation and hyphens. Best is to have small values for regular 11 In general the low level implementation can be optimized as there are better mechanisms in LuaTE X. 133 Extensions
Page 1:
explaining luatex and mkiv Fonts ou
Page 4 and 5:
2 Contents 5.4 Goodies 73 5.5 Analy
Page 6 and 7:
4 Contents
Page 8 and 9:
6 Introduction In this manual we wi
Page 10 and 11:
8 Font formats a b g l q . ; ? ffi
Page 12 and 13:
10 Font formats When T E X ships ou
Page 14 and 15:
12 A.4 A.3 Font formats multiple ac
Page 16 and 17:
14 Font formats can be rules that t
Page 18 and 19:
16 Font formats /fonts/tfm/vendor/t
Page 20 and 21:
18 Modes raw tfm normalized tfm raw
Page 22 and 23:
20 Modes shown next: kern cyrl dflt
Page 24 and 25:
22 Modes ccmp cyrl mkd абвгде
Page 26 and 27:
24 Modes dlig latn gag abcdefghijkl
Page 28 and 29:
26 Modes liga latn nsm abcdefghijkl
Page 30 and 31:
28 Modes salt latn mol abcdefghijkl
Page 32 and 33:
30 Modes glyph 256 font 42: U+00074
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
36 Modes optimizer that can apply a
Page 40 and 41:
38 Modes ا خǇَ﮲ ف﮲َ step
Page 42 and 43:
40 Modes dir +TRT glyph 256 font 49
Page 44 and 45:
42 Modes and now we get: 123 normal
Page 46 and 47:
44 Modes MkIV run can be faster tha
Page 48 and 49:
46 Lookups \font \MyFontG = lmr12 s
Page 50 and 51:
48 Lookups 3.4 Name Say that we wan
Page 52 and 53:
50 Lookups We add another specifier
Page 54 and 55:
52 Methods \definefont [MyFont] [Bo
Page 56 and 57:
54 Methods } copyright = "ConTeXt d
Page 58 and 59:
56 Features of all, all we get to s
Page 60 and 61:
58 Features in base mode. A single
Page 62 and 63:
60 Features accumulate within a wor
Page 64 and 65:
62 Features features analyze=yes, c
Page 66 and 67:
64 Features \definedfont[lmroman10-
Page 68 and 69:
66 Features single substitutions or
Page 70 and 71:
68 F -0.492 eatures result ffi feat
Page 72 and 73:
70 Features font 80: lmroman10-regu
Page 74 and 75:
72 Features font 46: cambria.ttf @
Page 76 and 77:
74 Features } } This goodie file is
Page 78 and 79:
76 Features { name = "msbm10.tfm",
Page 80 and 81:
78 Features \starttypescript[somefo
Page 82 and 83:
80 Features \setupbodyfont [mojcasf
Page 84 and 85: 82 Features } normalweight = "extra
Page 86 and 87: 84 Features "QF.waqf", "SKTH.waqf",
Page 88 and 89: 86 Features featureset=smallcaps] O
Page 90 and 91: 88 Features } }, When defining the
Page 92 and 93: 90 Features local defaultfraction =
Page 94 and 95: 92 Features } } ["LMRoman-Bold"] =
Page 96 and 97: 94 Features In fact, in addition to
Page 98 and 99: 96 Features } This time the applica
Page 100 and 101: 98 Features step 1 I don't wanna kn
Page 102 and 103: 100 Features If you’re lucky your
Page 104 and 105: 102 Scripts
Page 121 and 122: However, when we go the other way,
Page 124: 122 Math the regular a--z character
Page 127 and 128: While there are lots of text fonts,
Page 129 and 130: 8 Extensions 8.1 Introduction One o
Page 131: [default] [itlc=5] This is demonstr
Page 136 and 137: 134 Extensions characters to improv
Page 138 and 139: 136 Extensions U+00079 0.05 y 0.05
Page 140 and 141: 138 Extensions protrusion classes T
Page 142 and 143: 140 Extensions [fonts.composing.def
Page 144 and 145: 142 } Extensions top = { x = -250,
Page 146 and 147: 144 Extensions
Page 148 and 149: 146 Hooks
Page 150 and 151: 148 ) Appendix (LIG C l O 10) (KRN
Page 152 and 153: 150 ) Appendix (KRN O 177 R 0.056)
Page 154 and 155: 152 Appendix Notice Copyright 2003-
Page 156 and 157: 154 Appendix ... KPX seven.prop hyp
Page 158 and 159: 156 Appendix name = , features = ,
Page 160 and 161: 158 Appendix [] = "", ... default =
Page 162: 160 Appendix A.10 Discretionary nod
show all

Hagen - Pragma ADE

Create successful ePaper yourself

Delete template?

Save as template?