Hagen - Pragma ADE

More documents

Recommendations

Info

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

42 Modes and now we get: 123 normal 123 oldstyle 123 olstyle smallcaps 123 oldstyle 123 smallcaps You can exercise some control with \resetfeature: \switchtobodyfont[pagella] 123 normal \addfeature [f:oldstyle] 123 oldstyle \addfeature [f:smallcaps] 123 olstyle smallcaps \resetfeature 123 reset \addfeature [f:oldstyle] 123 oldstyle \addfeature [f:smallcaps] 123 olstyle smallcaps Watch how we use the [] variant of the commands. The braced and bracketed variants behave the same. 123 normal 123 oldstyle 123 olstyle smallcaps 123 reset 123 oldstyle 123 olstyle smallcaps There is also a generic command \feature that takes two arguments. Below we show all calls, with long and short variants: \addfeature [f:mine] \feature [more][f:mine] \feature[+][f:mine] \subtractfeature [f:mine] \feature [less][f:mine] \feature[-][f:mine] \replacefeature [f:mine] \feature [new][f:mine] \feature[=][f:mine] \resetandaddfeature[f:mine] \feature[local][f:mine] \feature[!][f:mine] \revivefeature [f:mine] \feature [old][f:mine] \feature[>][f:mine] \resetfeature \feature[reset] \feature[
The Husayni font focusses on Arabic, which in itself has not that large an alphabet, but being an advanced script font, it has a lot of features and definitely a lot of rules. In terms of processing it’s safe to say that Latin is of average complexity. At most you will get some substitutions, like regular numerals being replaced by oldstyles, or ligature building, which involves a bit of analysis, and some kerning at the end. In base mode the substitutions have no overhead, simply because the character table already has references to the substituents and the replacement already takes place when defining the font. There ligature building and kerning are also fast because of the limited amount of lookups that also are already kept with the characters. In node mode however, the lists have to be parsed and tables have to be consulted so even Latin processing has some overhead: each glyph node is consulted and analyzed (either or not in its context), often multiple times. However, the code is rather optimized and we use caching of already analyzed data when possible. A cjk script is somewhat more complex on the one hand, but pretty simple on the other. Instead of font based kerning, we need to prevent or encourage breaks between certain characters. This information is not in the font and is processed otherwise but it does cost some time. The font part however is largely idle as there are no features to be applied. Even better, because the glyphs are large and the information density is high, the processing time per page is not much different from Latin. Base mode is good enough for most cjk. The Arabic script is another matter. There we definitely go beyond what base mode offers so we always end up in node mode. Also, because there is some analysis involved, quite some substitutions and in the end also positioning, these are the least efficient fonts in terms of processing time. Of course the fact that we mix directions also plays a role. If in the Husayni font you enable 30 features with an average of 5 rules per feature, a 300 character paragraph will take 45.000 actions. 4 When multiple fonts are combined in a paragraph there will be more sweeps over the list and of course the replacements also have to happen. In a time when the average photo camera produces megabyte pictures it makes no sense to whine about the size of a font file. On the other hand as each font eventually ends up in memory as a Lua table, it makes sense to optimize that bit. This is why fonts are converted into a more efficient intermediate table that is cached on disk. This makes loading a font quite fast and due to shared tables memory usage rather efficient. Of course a scaled instance has to be generated too, but that is acceptable. To some extent loading and defining a font also depends on the way the macro package is set up. When comparing LuaT E X with for instance pdfT E X or X Ǝ T E X you need to take into account that in ConT E Xt MkIV we tend to use OpenType fonts only so there are less fonts loaded than in a more traditional setup. In ConT E Xt startup time of MkIV is less than MkII although overall processing time is slower, which is due to Unicode being used and more functionality being provided. On the other hand, immediate METAPOST processing and more clever multipass handling wins back time. The impact of fonts on processing time in a regular document is therefore not that impressive. In practice a 4 For a modern machine this amount is no real issue, but as each action involves function calls and possibly some garbage collection there is some price to pay. 43 Modes
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 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 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 134 and 135:
132 Extensions \definefontfeature [
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?