<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Shaping and shape plans: HarfBuzz Manual</title>
-<meta name="generator" content="DocBook XSL Stylesheets Vsnapshot">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="index.html" title="HarfBuzz Manual">
-<link rel="up" href="pt01.html" title="Part I. User's manual">
+<link rel="up" href="user-manual.html" title="Part I. User's manual">
<link rel="prev" href="fonts-and-faces-variable.html" title="Working with OpenType Variable Fonts">
<link rel="next" href="shaping-opentype-features.html" title="OpenType features">
-<meta name="generator" content="GTK-Doc V1.32.1 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.32 (XML mode)">
<link rel="stylesheet" href="style.css" type="text/css">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="5"><tr valign="middle">
<td width="100%" align="left" class="shortcuts"></td>
<td><a accesskey="h" href="index.html"><img src="home.png" width="16" height="16" border="0" alt="Home"></a></td>
-<td><a accesskey="u" href="
pt01.html"><img src="up.png" width="16" height="16" border="0" alt="Up"></a></td>
+<td><a accesskey="u" href="
user-manual.html"><img src="up.png" width="16" height="16" border="0" alt="Up"></a></td>
<td><a accesskey="p" href="fonts-and-faces-variable.html"><img src="left.png" width="16" height="16" border="0" alt="Prev"></a></td>
<td><a accesskey="n" href="shaping-opentype-features.html"><img src="right.png" width="16" height="16" border="0" alt="Next"></a></td>
</tr></table>
<p>
If a font has a GDEF table, then that is used for
glyph classes; if not, HarfBuzz will fall back to Unicode
- categorization by code point. If a font has an AAT "morx" table,
+ categorization by code point. If a font has an AAT <code class="literal">morx</code> table,
then it is used for substitutions; if not, but there is a GSUB
table, then the GSUB table is used. If the font has an AAT
- "kerx" table, then it is used for positioning; if not, but
+ <code class="literal">kerx</code> table, then it is used for positioning; if not, but
there is a GPOS table, then the GPOS table is used. If neither
- table is found, but there is a "kern" table, then HarfBuzz will
- use the "kern" table. If there is no "kerx", no GPOS, and no
- "kern", HarfBuzz will fall back to positioning marks itself.
+ table is found, but there is a <code class="literal">kern</code> table, then HarfBuzz will
+ use the <code class="literal">kern</code> table. If there is no <code class="literal">kerx</code>, no GPOS, and no
+ <code class="literal">kern</code>, HarfBuzz will fall back to positioning marks itself.
</p>
<p>
With a well-behaved OpenType font, you expect GDEF, GSUB, and
</div>
</div>
<div class="footer">
-<hr>Generated by GTK-Doc V1.32.1</div>
+<hr>Generated by GTK-Doc V1.32</div>
</body>
</html>
\ No newline at end of file
projects / platform / upstream / harfbuzz.git / blobdiff