The Communications of the TEX Users Group Volume 29 ... - TUG

More documents

Recommendations

Info

$E-m: Guidelines for Future TEX Extensions - TUG$

$TUG 2001: A TEX Odyssey PROGRAM$

$LATEX Sophisticated professional typesetting for business and ...$

$TEX and Scripting Languages - TUG$

$Geometric Diversions with TEX, METAFONT and METAPOST - TUG$

$Writing Gregg Shorthand with mEtaFoNt and LATEX - TUG$

$Generating LaTeX documents through Matlab - TUG$

Dave Crossland References [1] http://en.wikipedia.org/wiki/Category: Personality_typologies [2] Keirsey, D. Please Understand Me II: Temperament, Character, Intelligence. 1998: Prometheus Nemesis. [3] Knuth, D. Digital typography. 1999: CSLI. [4] Knuth, D. & Zapf, H. AMS Euler: A New Typeface for Mathematics. 1989: Scholarly Publishing. [5] http://fontforge.sourceforge.net [6] http://tug.org/texworks/ [7] http://www.scribus.net [8] http://itexmac.sourceforge.net/SyncTeX. html [9] http://lilypond.org/mftrace/ [10] http://www.tug.org/metapost.html [11] http://www.ctan.org/tex-archive/fonts/ utilities/metatype1/ [12] Osinga, F. Science, Strategy and War: The Strategic Theory of John Boyd. 2006: Routledge. [13] Sherif, A. and Fahmy, H. Meta-designing parameterized Arabic fonts for AlQalam. In this volume, 435–443. [14] http://www.inkscape.org [15] http://metafont.tutorial.free.fr Copyright c○ 2008 Dave Crossland. Verbatim copying and redistribution of this entire article is permitted, provided this notice is preserved. 420 TUGboat, Volume 29 (2008), No. 3 — Proceedings of the 2008 Annual Meeting
Creating cuneiform fonts with MetaType1 and FontForge Karel Píška Institute of Physics of the ASCR, v. v. i. CZ-182 21 Prague, Czech Republic piska (at) fzu dot cz 1 Introduction Abstract A cuneiform font collection covering Akkadian, Ugaritic and Old Persian glyph subsets (about 600 signs) has been produced in two steps. With MetaType1 we generate intermediate Type 1 fonts, and then construct OpenType fonts using FontForge. We describe cuneiform design and the process of font development. I am interested in scripts, alphabets, writing systems, and in fonts, their computer representation. Ten years ago I decided to create Type 1 fonts for cuneiform, and last year, to extend them to Unicode OpenType versions. In my older Type 1 version (1998/9) [4] the raw text was written ‘by hand’ and then directly compiled into Type 1 with t1asm from t1utils [10]. The glyph set consisted of several separate Type 1 components to cover Akkadian (according to Labat) in a ‘Neo-Assyrian’ form (three files), Ugaritic, and Old Persian. Three books served as principal sources: two Akkadian syllabaries edited by R. Labat [1] and F. Thureau-Dangin [2], and the encyclopedia The World’s Writing Systems [3]. No scanning of pictures or clay tablets was performed. The fonts are based on a starting point — my simple design of wedges in three variant forms (see also Fig. 1, below): �� endfont A ‘Academic’ B ‘Bold (Filled)’ C ‘Classic’ Our aim is to use free and open source software to produce “open source fonts”. Thus, to create the fonts only non-proprietary tools have been employed: MetaType1; FontForge; t1utils, gawk; other standard Unix utilities such as bash, sed, sort, . . . In the following sections we will explain the process of creating fonts and illustrate it with numerous examples. 2 Producing Type 1 with MetaType1 The MetaType1 package [6], developed by the authors of Latin Modern, TEX Gyre and other font collections (B. Jackowski, J. Nowacki, P. Strzelczyk): • runs METAPOST (any available version) to produce eps files with outlines for all glyphs; • collects all the data into one Type 1 file. The information about the font and its glyphs is described in the METAPOST source files; addi- tional macros are defined in MetaType1 extensions or may be appended by the user. For illustrations see the examples below. An explanation of some technical details and techniques how to work with MetaType1 can be found in the tutorial written by Klaus Höppner [7], which also includes a simple complete example and Makefile. 2.1 Font description in MetaType1 As usual with METAFONT or METAPOST the compilation is invoked by a main control file — naakc.mp: input fontbase; use_emergency_turningnumber; input naak.mpe; maybeinput "naakc.mpd"; maybeinput "naakc.mph"; maybeinput "naug.mph"; maybeinput "naop.mph"; beginfont maybeinput "naak.mpg"; maybeinput "naug.mpg"; maybeinput "naop.mpg"; Global font parameters may be defined in a font header file — naakc.mph: % FONT INFORMATION pf_info_familyname "NeoAssyrianClassicType1"; pf_info_weight "Medium"; pf_info_fontname "NeoAssyrianClassicType1"; pf_info_version "002.001"; pf_info_author "Karel Piska at fzu.cz 2008"; pf_info_italicangle 0; pf_info_underline -100, 50; pf_info_fixedpitch false; pf_info_adl 750, 250, 0; italic_shift:=0; Internal glyph names and metric data can be assigned as follows: % INTRODUCE CHARS standard_introduce("ash.akk"); standard_introduce("hal.akk"); standard_introduce("mug.akk"); TUGboat, Volume 29 (2008), No. 3 — Proceedings of the 2008 Annual Meeting 421
Page 1 and 2:
The Communications of the TEX Users
Page 3 and 4:
TUG2008 Proceedings University Coll
Page 5 and 6:
TUG 2008—program Monday, July 21
Page 7 and 8:
At the reception. Around the front
Page 9 and 10:
Taco Hoekwater, inside the Beamish
Page 11 and 12:
Another, equally large, disadvantag
Page 13 and 14:
This “saves” the original \text
Page 15 and 16:
Figure 5: Macro result pushed back
Page 17 and 18:
TEXworks: Lowering the barrier to e
Page 19 and 20:
Direct and reverse synchronization
Page 21 and 22:
The TEXnical terms used to describe
Page 23 and 24: 6.2 An orthogonal implementation On
Page 25 and 26: In fact, the text editors and the v
Page 27 and 28: albanian greek norwegian belarusian
Page 29 and 30: input manually, but are generated b
Page 31 and 32: 1.2 Commercially available software
Page 33 and 34: If L ATEX can fit the snippet into
Page 35 and 36: Pascal MetaPost, but using CWEB as
Page 37 and 38: The TEX-Lua mix Hans Hagen Pragma A
Page 39 and 40: \setbox0=\hbox{x}\the\wd0 In Lua we
Page 41 and 42: start.char = uc return true end end
Page 43 and 44: stream-based approach, this time th
Page 45 and 46: example is support for OpenType fon
Page 47 and 48: typesetting system is TEX [4] creat
Page 49 and 50: 13. Image conversion from various f
Page 51 and 52: the mapping file example.paraStyleN
Page 53 and 54: The second author accepts or reject
Page 55 and 56: Languages for bibliography styles J
Page 57 and 58: @STRING{srd = {Stephen Reeder Donal
Page 59 and 60: # # standard footnote format (latex
Page 61 and 62: . , \bbled \bbleds .
Page 63 and 64: Languages for bibliography styles (
Page 65 and 66: References [1] James C. Alexander:
Page 67 and 68: Vistas for TEX: liberate the typogr
Page 69 and 70: - even direct formatting instructio
Page 71 and 72: e that quick, simple and clear rend
Page 73: see that there are slight differenc
Page 77 and 78: Definition of encoding (Unicode) Pl
Page 79 and 80: epresentation with proper path dire
Page 81 and 82: When it came to implementing the T1
Page 83 and 84: 4.3 OpenType math in new TEX engine
Page 85 and 86: However, there have always been exc
Page 87 and 88: [2] Nelson Beebe: Character set enc
Page 89 and 90: Meta-designing parameterized Arabic
Page 91 and 92: on the pen direction at each point
Page 93 and 94: % Description for isolated ’alif
Page 95 and 96: Figure 15: Tracing a word from left
Page 97 and 98: Table 1 shows the MOS scores for in
Page 99 and 100: P3 P3 P3 Q2 Q2 Q2 � � W3 W3 W3
Page 101 and 102: abridged form, it looks like this:
Page 103 and 104: with extensions is still somewhat m
Page 105 and 106: local rx, ry = second.y_coord - ty,
Page 107 and 108: \startreusableMPgraphic{name}... \s
Page 109 and 110: the macro \testengine sees two argu
Page 111 and 112: and exhyph-uk.tex, respectively. Th
Page 113 and 114: stand for markers of semiconsonants
Page 115 and 116: y finite state transducers (FSTs).
Page 117 and 118: local p = hpack(copy(h.list)) lastl
Page 119 and 120: with PDF documents. Several new tec
Page 121 and 122: Advanced features for publishing ma
Page 123 and 124: Advanced features for publishing ma
Page 125 and 126:
— — — — — — — — Fig
Page 127 and 128:
Advanced features for publishing ma
Page 129 and 130:
telegraph. The relatively recent di
Page 131 and 132:
1: [ type: unichar, code: 0073 ] ]
Page 133 and 134:
5 Conclusions The model introduced
Page 135 and 136:
4 Why TEX files and not other marku
Page 137 and 138:
The galley Module or: How I Learned
Page 139:
TUGboat, Volume 29 (2008), No. 3 48
Page 142 and 143:
488 TUGboat, Volume 29 (2008), No.
Page 144 and 145:
TUGBOAT Volume 29 (2008), No. 3 Tab
show all

The Communications of the TEX Users Group Volume 29 ... - TUG

Create successful ePaper yourself

Delete template?

Save as template?