1<HTML>
2<HEAD>
3
4<TITLE>TTX Documentation</TITLE>
5
6
7</HEAD>
8<BODY bgcolor="#FFFFFF">
9
10<H3>TTX -- From OpenType and TrueType to XML and Back</H3>
11
12<A HREF="http://fonttools.sourceforge.net/">TTX</A> is a tool for manipulating TrueType and OpenType fonts. It is written in Python and has a BSD-style, open-source licence -- see LICENSE.txt. Among other things this means you can use it free of charge. It's hosted at <A HREF="http://sourceforge.net/">sourceforge.net</A>.
13
14<P>
15TTX can dump TrueType and OpenType fonts to an XML-based text format, which is also called TTX. TTX files have a .ttx file extension.
16
17<H3>How to use TTX</H3>
18
19The TTX application works can be used in two ways, depending on what platform you run it on:
20
21<ul>
22  <li>As a command line tool (Windows/DOS, Unix, MacOSX)</li>
23  <li>By dropping files onto the application (Windows, MacOS)</li>
24</ul>
25
26<P>
27TTX detects what kind of files it is fed: it will output a .ttx file when it sees a .ttf or .otf, and it will compile a .ttf or .otf when the input file is a .ttx file. By default, the output file is created in the same folder as the input file, and will have the same name as the input file but with a different extension. TTX will <I>never</I> overwrite existing files, but if necessary will append a unique number to the output filename (before the extension), eg.: "Arial#1.ttf".
28
29<P>
30When using TTX from the command line there are a bunch of extra options, these are explained in the help text, as displayed when typing "ttx -h" at the command prompt. These additional options include:
31<ul>
32  <li>specifying the folder where the output files are created</li>
33  <li>specifying which tables to dump or which tables to exclude</li>
34  <li>merging partial .ttx files with existing .ttf or .otf files</li>
35  <li>listing brief table info isntead of dumping to .ttx</li>
36  <li>splitting tables to separate .ttx files</li>
37  <li>disabling TT instruction disassembly</li>
38</ul>
39
40<H3>The TTX file format</H3>
41
42The following tables are currently supported:
43<BLOCKQUOTE><TT>
44<!-- begin table list -->
45BASE, CBDT, CBLC, CFF, COLR, CPAL, DSIG, EBDT, EBLC, FFTM, GDEF, GMAP, GPKG, GPOS, GSUB, JSTF, LTSH, META, OS/2, SING, SVG, TSI0, TSI1, TSI2, TSI3, TSI5, TSIB, TSID, TSIJ, TSIP, TSIS, TSIV, VORG, cmap, cvt, fpgm, gasp, glyf, hdmx, head, hhea, hmtx, kern, loca, maxp, name, post, prep, sbix, vhea and vmtx
46<!-- end table list -->
47</TT></BLOCKQUOTE>
48Other tables are dumped as hexadecimal data.
49
50<P>
51TrueType fonts use glyph indices (GlyphID's) to refer to glyphs in most places.
52While this is fine in binary form, it is really hard to work with for
53humans. Therefore we use names instead.
54
55<P>The glyph names are either extracted from the 'CFF ' table or the 'post' table,
56or are derived from a Unicode 'cmap' table. In the latter case the Adobe Glyph List
57is used to calculate names based on Unicode values. If all of these mthods fail,
58names are invented based on GlyphID (eg. "glyph00142").
59
60<P>It is possible that different glyphs use the same name. If this happens,
61we force the names to be unique by appending "#n" to the name (n being an
62integer number). The original names are being kept, so this has no influence
63on a "round tripped" font.
64
65<P>Because the order in which glyphs are stored inside the TT font is
66important, we maintain an ordered list of glyph names in the font.
67
68
69<H3>Development and feedback</H3>
70
71TTX/FontTools development is ongoing, but often goes in spurts. Feature requests and bug reports are always welcome. The best place for these is currently the fonttools-discussion mailing list at SourceForge. This list is both for discussion TTX from an end-user perspective as well as TTX/FontTools development. Subscription info can be found if you follow the "Mailing Lists" link at the <A HREF="http://sourceforge.net/projects/fonttools/">SourceForge project page</A>. You can also email me directly at <A HREF="mailto:just@letterror.com">just@letterror.com</A>.
72
73<P>
74Let me take this opportunity to mention that if you have special needs (eg. custom font monipulators, dufferent table formats, etc.): I am available for contracting.
75
76<H3>Credits</H3>
77
78Windows setup script: Adam Twardoch
79<BR>Icon: Hannes Famira
80
81<H3>Acknowledgements</H3>
82
83(in alphabetical order)
84Erik van Blokland, Petr van Blokland, Jelle Bosma, Vincent Connare,
85Simon Daniels, Hannes Famira, Yannis Haralambous, Greg Hitchcock, John Hudson,
86Jack Jansen, Tom Kacvinsky, Antoine Leca, Werner Lemberg, Tal Leming,
87Peter Lofting, Dave Opstad, Laurence Penney, Read Roberts, Guido van Rossum, Andreas Seidel, Adam Twardoch.
88
89<H3>Copyrights</H3>
90
91<A HREF="http://fonttools.sourceforge.net/">FontTools/TTX</A>
92<BR>1999-2003 Just van Rossum; LettError (just@letterror.com). See LICENSE.txt for the full license.
93<P>
94<A HREF="http://www.python.org/">Python</A>
95<BR>Copyright (c) 2001-2003 Python Software Foundation. All Rights Reserved.
96<BR>Copyright (c) 2000 BeOpen.com. All Rights Reserved.
97<BR>Copyright (c) 1995-2001 Corporation for National Research Initiatives. All Rights Reserved.
98<BR>Copyright (c) 1991-1995 Stichting Mathematisch Centrum, Amsterdam. All Rights Reserved.
99<P>
100<A HREF="http://www.pfdubois.com/numpy/">Numeric Python (NumPy)</A>
101<BR>Copyright (c) 1996. The Regents of the University of California. All rights reserved.
102
103</BODY>
104</HTML>
105