1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300 1301 1302 1303 1304 1305 1306 1307 1308 1309 1310 1311 1312 1313 1314 1315 1316 1317 1318 1319 1320 1321 1322 1323 1324 1325 1326 1327 1328 1329 1330 1331 1332 1333 1334 1335 1336 1337 1338 1339 1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1350 1351 1352 1353 1354 1355 1356 1357 1358 1359 1360 1361 1362 1363 1364 1365 1366 1367 1368 1369 1370 1371 1372 1373 1374 1375 1376 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1391 1392 1393 1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 1410 1411 1412 1413 1414 1415 1416 1417 1418 1419 1420 1421 1422 1423 1424 1425 1426 1427 1428 1429 1430 1431 1432 1433 1434 1435 1436 1437 1438 1439 1440 1441 1442 1443 1444 1445 1446 1447 1448 1449 1450 1451 1452 1453 1454 1455 1456 1457 1458 1459 1460 1461 1462 1463 1464 1465 1466 1467 1468 1469 1470 1471 1472 1473 1474 1475 1476 1477 1478 1479 1480 1481 1482 1483 1484 1485 1486 1487 1488 1489 1490 1491 1492 1493 1494 1495 1496 1497 1498 1499 1500 1501 1502 1503 1504 1505 1506 1507 1508 1509 1510 1511 1512 1513 1514 1515 1516 1517 1518 1519 1520 1521 1522 1523 1524 1525 1526 1527 1528 1529 1530 1531 1532 1533 1534 1535 1536 1537 1538 1539 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 1557 1558 1559 1560 1561 1562 1563 1564 1565 1566 1567 1568 1569 1570 1571 1572 1573 1574 1575 1576 1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 1590 1591 1592 1593 1594 1595 1596 1597 1598 1599 1600 1601 1602 1603 1604 1605 1606 1607 1608 1609 1610 1611 1612 1613 1614 1615 1616 1617 1618 1619 1620 1621 1622 1623 1624 1625 1626 1627 1628 1629 1630 1631 1632 1633 1634 1635 1636 1637 1638 1639 1640 1641 1642 1643 1644 1645 1646 1647 1648 1649 1650 1651 1652 1653 1654 1655 1656 1657 1658 1659 1660 1661 1662 1663 1664 1665 1666 1667 1668 1669 1670 1671 1672 1673 1674 1675 1676 1677 1678 1679 1680 1681 1682 1683 1684 1685 1686 1687 1688 1689 1690 1691 1692 1693 1694 1695 1696 1697 1698 1699 1700 1701 1702 1703 1704 1705 1706 1707 1708 1709 1710 1711 1712 1713 1714 1715 1716 1717 1718 1719 1720 1721 1722 1723 1724 1725 1726 1727 1728 1729 1730 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760 1761 1762 1763 1764 1765 1766 1767 1768 1769 1770 1771 1772 1773 1774 1775 1776 1777 1778 1779 1780 1781 1782 1783 1784 1785 1786 1787 1788 1789 1790 1791 1792 1793 1794 1795 1796 1797 1798 1799 1800 1801 1802 1803 1804 1805 1806 1807 1808 1809 1810 1811 1812 1813 1814 1815 1816 1817 1818 1819 1820 1821 1822 1823 1824 1825 1826 1827 1828 1829 1830 1831 1832 1833 1834 1835 1836 1837 1838 1839 1840 1841 1842 1843 1844 1845 1846 1847 1848 1849 1850 1851 1852 1853 1854 1855 1856 1857 1858 1859 1860 1861 1862 1863 1864 1865 1866 1867 1868 1869 1870 1871 1872 1873 1874 1875 1876 1877 1878 1879 1880 1881 1882 1883 1884 1885 1886 1887 1888 1889 1890 1891 1892 1893 1894 1895 1896 1897 1898 1899 1900 1901 1902 1903 1904 1905 1906 1907 1908 1909 1910 1911 1912 1913 1914 1915 1916 1917 1918 1919 1920 1921 1922 1923 1924 1925 1926 1927 1928 1929 1930 1931 1932 1933 1934 1935 1936 1937 1938 1939 1940 1941 1942 1943 1944 1945 1946 1947 1948 1949 1950 1951 1952 1953 1954 1955 1956 1957 1958 1959 1960 1961 1962 1963 1964 1965 1966 1967 1968 1969 1970 1971 1972 1973 1974 1975 1976 1977 1978 1979 1980 1981 1982 1983 1984 1985 1986 1987 1988 1989 1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 2026 2027 2028 2029 2030 2031 2032 2033 2034 2035 2036 2037 2038 2039 2040 2041 2042 2043 2044 2045 2046 2047 2048 2049 2050 2051 2052 2053 2054 2055 2056 2057 2058 2059 2060 2061 2062 2063 2064 2065 2066 2067 2068 2069 2070 2071 2072 2073 2074 2075 2076 2077 2078 2079 2080 2081 2082 2083 2084 2085 2086 2087 2088 2089 2090 2091 2092 2093 2094 2095 2096 2097 2098 2099 2100 2101 2102 2103 2104 2105 2106 2107 2108 2109 2110 2111 2112 2113 2114 2115 2116 2117 2118 2119 2120 2121 2122 2123 2124 2125 2126 2127 2128 2129 2130 2131 2132 2133 2134 2135 2136 2137 2138 2139 2140 2141 2142 2143 2144 2145 2146 2147 2148 2149 2150 2151 2152 2153 2154 2155 2156 2157 2158 2159 2160 2161 2162 2163 2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 2178 2179 2180 2181 2182 2183 2184 2185 2186 2187 2188 2189 2190 2191 2192 2193 2194 2195 2196 2197 2198 2199 2200 2201 2202 2203 2204 2205 2206 2207 2208 2209 2210 2211 2212 2213 2214 2215 2216 2217 2218 2219 2220 2221 2222 2223 2224 2225 2226 2227 2228 2229 2230 2231 2232 2233 2234 2235 2236 2237 2238 2239 2240 2241 2242 2243 2244 2245 2246 2247 2248 2249 2250 2251 2252 2253 2254 2255 2256 2257 2258 2259 2260 2261 2262 2263 2264 2265 2266 2267 2268 2269 2270 2271 2272 2273 2274 2275 2276 2277 2278 2279 2280 2281 2282 2283 2284 2285 2286 2287 2288 2289 2290 2291 2292 2293 2294 2295 2296 2297 2298 2299 2300 2301 2302 2303 2304 2305 2306 2307 2308 2309 2310 2311 2312 2313 2314 2315 2316 2317 2318 2319 2320 2321 2322 2323 2324 2325 2326 2327 2328 2329 2330 2331 2332 2333 2334 2335 2336 2337 2338 2339 2340 2341 2342 2343 2344 2345 2346 2347 2348 2349 2350 2351 2352 2353 2354 2355 2356 2357 2358 2359 2360 2361 2362 2363 2364 2365 2366 2367 2368 2369 2370 2371 2372 2373 2374 2375 2376 2377 2378 2379 2380 2381 2382 2383 2384 2385 2386 2387 2388 2389 2390 2391 2392 2393 2394 2395 2396 2397 2398 2399 2400 2401 2402 2403 2404 2405 2406 2407 2408 2409 2410 2411 2412 2413 2414 2415 2416 2417 2418 2419 2420 2421 2422 2423 2424 2425 2426 2427 2428 2429 2430 2431 2432 2433 2434 2435 2436
|
<HTML>
<HEAD>
<!-- Created with AOLpress/2.0 -->
<!-- AP: Created on: 7-Mar-2001 -->
<!-- AP: Last modified: 11-Sep-2009 -->
<TITLE>Frequently Asked Questions</TITLE>
<LINK REL="icon" href="ffanvil16.png">
<LINK REL="stylesheet" TYPE="text/css" HREF="FontForge.css">
</HEAD>
<BODY id="framed">
<P ALIGN=CENTER>
<IMG SRC="fontforge-banner-420.jpeg" WIDTH=420 HEIGHT=80>
<DIV id="framed-in">
<TABLE ALIGN="Right">
<TR>
<TD><A HREF="faqFS.html" TARGET="_top">Frames</A></TD>
</TR>
</TABLE>
<H1 ALIGN=Center>
Frequently Asked Questions<BR>
<SMALL>(or many of the questions I've been asked so far)</SMALL>
</H1>
<TABLE>
<TR>
<TD>
</TD>
<TD><BLOCKQUOTE ID="lit">
<B><SMALL>Sir Toby:</SMALL></B>Thy most exquisite reason, dear knight?<BR>
<B><SMALL>Sir Andrew</SMALL></B> I have no exquisite reason for't,<BR>
but I have reason good enough
<P ALIGN=RIGHT>
<SMALL>Twelfth Night, II, iii, 130<BR>
Shakespeare</SMALL>
</BLOCKQUOTE>
</TD>
</TR>
</TABLE>
<H2>
Most important question
</H2>
<UL>
<LI>
How do I find something in the manual?
<FORM method=GET action="http://www.google.com/search">
<INPUT type=hidden name="as_sitesearch" value="fontforge.sourceforge.net">
<INPUT type=text name="as_q">
<INPUT type=submit name="btnG" value="Search">(Powered by
<A HREF="http://www.google.com/">Google</A>)
</FORM>
</UL>
<H2>
General questions about FontForge
</H2>
<UL>
<LI>
<A HREF="#font-editor">Why a font editor, aren't there enough fonts
already?</A>
<UL>
<LI>
<A HREF="#write">Why did I write it?</A>
<LI>
<A HREF="#give">Why do I give it away?</A>
<LI>
<A HREF="#Pots">Does working on FontForge provide the same kind of pleasure
as working on pots or baking bread?</A>
<LI>
<A HREF="faq.html#native">Why doesn't it use the native MS Windows or Mac
windowing system?</A>
<LI>
<A HREF="#widget-set">Why is FontForge based on a non-standard widget set?</A>
<LI>
<A HREF="#C-plus-plus">Why isn't FontForge written in C++? (or <I>Why C++
is not my favorite language</I>)</A>
<LI>
<A HREF="faq.html#bsd-license">Why do I release FontForge under the BSD license
and not GPL?</A>
<LI>
<A HREF="#libraries">Why does FontForge load libraries at run time rather
than being linked with them?</A>
<LI>
<A HREF="#roadmap">Why is there no future roadmap for FontForge?</A>
</UL>
</UL>
<H2>
General questions about fonts
</H2>
<UL>
<LI>
<A HREF="#legal">Is it legal to modify a font? Is it ethical?</A>
<LI>
<A HREF="#pointsize">What is a 12point font?</A> (What measurement of the
font determines the point size)
<UL>
<LI>
<A HREF="#linespace">How do I set the line spacing on a font?</A>
</UL>
<LI>
<A HREF="#em-units">How big will my glyph be? (What are em-units?)</A>
<LI>
<A HREF="#license">What's a good license to use on an open source font?</A>
</UL>
<H2>
Using FontForge & Installing fonts on various systems
</H2>
<UL>
<LI>
How do I install FontForge on:
<TABLE CELLSPACING="6" CELLPADDING="2">
<TR>
<TD><P ALIGN=Center>
<A HREF="nix-install.html" TARGET="_top">Unix/Linux</A></TD>
<TD> <A HREF="mac-install.html" TARGET="_top">Mac</A></TD>
<TD> <A HREF="ms-install.html" TARGET="_top">MS/Windows</A></TD>
<TD> <A HREF="vms-install.html" TARGET="_top">VMS</A></TD>
<TD> <A HREF="source-build.html" TARGET="_top">from source</A></TD>
</TR>
</TABLE>
<LI>
<A HREF="running.html#cygwin-troubles" TARGET="_top">Why does nothing happen
when I type "$ <TT>fontforge</TT>" on cygwin?</A>
<LI>
<A HREF="#Minimum">Minimum requirements</A>
<UL>
<LI>
<A HREF="#excessive-memory">Why does FontForge use so much memory?</A>
</UL>
<LI>
<A HREF="#font-install">How do I install the fonts once I've made them?</A>
<LI>
<A HREF="faq.html#Bad-Windows-Install">Why won't FontForge's fonts install
on some MS Windows systems</A>
<LI>
<A HREF="#How-mac">How do I edit fonts from my macintoy?</A>
<UL>
<LI>
<A HREF="#How-family">How do I create a mac font family? (How do I get the
mac to group my fonts so that the italic and bold styles work)?</A>
<LI>
<A HREF="#Mac-ATM">Why doesn't ATM work with my fonts?</A>
</UL>
<LI>
<A HREF="#windows">How do I edit fonts on MS windows?</A>
<UL>
<LI>
<A HREF="faq.html#Bad-Windows-Fonts">Why don't my fonts work on windows?</A>
</UL>
<LI>
<A HREF="#otf-diffs">I generated an opentype (or truetype) font and windows
wouldn't install it. Why not?</A>
<LI>
<A HREF="#DSIG">I have a truetype font with opentype tables, but windows
displays the "TT" (truetype) icon and not the "O" icon. Why?</A>
<LI>
<A HREF="#names">What do all the different font names mean?</A>
</UL>
<H2>
Font Conversions
</H2>
<UL>
<LI>
<A HREF="faq.html#outline-conversion">Converting from one outline format
to another</A>
<LI>
<A HREF="faq.html#bitmap-conversion">Converting from one bitmap format to
another</A>
<LI>
<A HREF="#outline-bitmap">Converting from an outline format to a bitmap</A>
<LI>
<A HREF="faq.html#bitmap-outline">Converting from a bitmap format to an
outline</A>
<LI>
<A HREF="#AAT2OT">Converting from Apple's Advanced Typography to OpenType</A>
<LI>
<A HREF="#OT2AAT">Converting from OT to AAT</A>
<LI>
<A HREF="#Inkscape">Importing glyphs from Inkscape</A>
</UL>
<H2>
Questions about Hints and TrueType Instructions
</H2>
<UL>
<LI>
<A HREF="#hint-subs">How do I make it use hint substitution?</A>
<LI>
<A HREF="#flex-hints">How do I make it use flex hints?</A>
<UL>
<LI>
<A HREF="#flex2">How can I tell if it is going to use flex hints?</A>
</UL>
<LI>
<A HREF="#fuzzy">My glyphs are all perfectly hinted, why do some stems have
different widths (or appear fuzzy, or fade away completely)?</A>
<LI>
<A HREF="#ttf-degrade">I loaded a ttf font, made a few changes and generated
a new font. The changed glyphs don't look anywhere near as nice as the originals.
Why?</A>
</UL>
<H2>
Questions about <A HREF="bibliography.html" TARGET="_top">Font Formats</A>
</H2>
<UL>
<LI>
<A HREF="faq.html#Open-difference">What's the difference between OpenType
and PostScript (or TrueType) fonts?</A>
<LI>
<A HREF="faq.html#AAT-Open">What is the difference between AAT (Apple Advanced
Typography) and OpenType?</A>
<LI>
<A HREF="#Tiger-Open">Why does a font, which worked fine under 10.3 fail
on Mac 10.4 (Tiger)?</A>
<LI>
<A HREF="#cidmaps">What on earth are the cidmap files, and should I care
about them?</A>
<UL>
<LI>
<A TARGET="_top" HREF="cidmenu.html#CID">(What is a CID-keyed font?)</A>
</UL>
<LI>
<A HREF="faq.html#TeX">Why doesn't TeX work with my fonts?</A>
<UL>
<LI>
<A HREF="#mf-files">Why doesn't FontForge let me edit an '.mf' file?</A>
</UL>
<LI>
<A HREF="#non-integral">Is it safe to use non-integral coordinates? Will
it screw up in Word or anything?</A>
<LI>
<A HREF="#Open-size">Why isn't my Open Type font much smaller than the .pfb
file?</A>
<LI>
<A HREF="#Missing-Refs">When I load an otf or a type1 font most of my references
have been replaced by inline copies. How do I get my references back?</A>
<LI>
<A HREF="#kern-info">Does FontForge read in the old kerning information from
fonts?</A>
<LI>
<A HREF="#mensis">How do I set a particular bit in the OS/2 table (or any
other)?</A>
<LI>
<A href="#sfd">What's an sfd file?</A>
<UL>
<LI>
<A HREF="#excessive-memory">Why are they so big?</A>
</UL>
</UL>
<H2>
Mathematical questions
</H2>
<UL>
<LI>
<A HREF="#simplify">Does the simplify command lose accuracy?</A>
<LI>
<A HREF="#cubic-quadratic">How does FontForge convert a cubic spline into
a quadratic spline for truetype?</A>
<LI>
<A HREF="#quadratic-cubic">How does FontForge convert a quadratic spline
into a cubic (when reading truetype)?</A>
</UL>
<H2>
Image file questions
</H2>
<UL>
<LI>
<A HREF="#dynamic-libs">Why does fontforge say "Error loading dynamic library"
when trying to import an image file?</A>
<LI>
<A HREF="#complex-eps">Why does fontforge say "EPS file is too complex to
be understood"?</A>
<LI>
<A HREF="#Inkscape">Importing glyphs from Inkscape</A>
</UL>
<H2>
Random questions
</H2>
<UL>
<LI>
<A HREF="#background">FontForge's grey background distesses me. How do I
change it?</A>
<LI>
<A HREF="#fontsize">The fonts FontForge uses in its GUI are too small (too
big) how do I change them?</A>
<LI>
<A HREF="#monospace">How do I mark a font as monospaced?</A>
<LI>
<A HREF="#new-encoding">How do I tell fontforge about a new encoding?</A>
<LI>
<A HREF="#new-name">How do I add a glyph with a new name?</A>
<LI>
<A HREF="#glyphnames">Why does fontforge give some glyphs the wrong name?</A>
<LI>
<A HREF="#save-no-change">After I generate a font and quit, why does FontForge
ask if I want to save the font? I didn't change anything.</A>
<LI>
<A HREF="#minify-iconify">Why does my window get iconified when I want to
minify the view?</A>
<LI>
<A HREF="#no-mu">Why isn't there a character named "mu" in my greek font?</A>
(or "Delta", or "Omega", or "pi1")
<LI>
<A HREF="#no-copy-names">Why doesn't Edit->Copy copy glyph names as well
as glyph info?</A>
<LI>
<A HREF="#copy-names">Why does Edit->Paste complain about name
duplication?</A>
<LI>
<A HREF="faq.html#default-char">How do I set the default glyph of a font?</A>
<LI>
<A HREF="#mingliu">I looked at kaiu.ttf or mingliu.ttf and the outlines looked
nothing like the correct glyphs. What's wrong?</A>
<LI>
<A HREF="#greek-accents">When I use Element->Build->Build Accented
Glyph to build one of the Extended Greek glyphs (U+1F00-U+1FFF) FontForge
picks the wrong accents. Why?</A>
<LI>
<A HREF="#u-accents">When I use Element->Build->Build Accented Glyph
to build accents over "u" or "y" I get the accent over one of the stems not
centered on the glyph. Why?</A>
<LI>
<A HREF="#ttf2afm">Why does ttf2afm crash on FontForge ttf files?</A>
<LI>
<A TARGET="_top" HREF="index.html#known-bugs">Where can I find a list of
known bugs in FontForge?</A>
<LI>
<A HREF="#memory">My system keeps crashing because FontForge keeps running
out of memory. What can I do about it?</A>
<LI>
<A HREF="#Unstable">Why is FontForge so unstable?</A>
<LI>
<A HREF="#Compiz">Why does FontForge look ugly under Xgl/Compiz?</A>
<LI>
<A HREF="#talk">Why don't I talk at conferences?</A>
<LI>
<A HREF="source-build.html#patch" TARGET="_top">How do I use a patch file?</A>
</UL>
<P>
<HR>
<DL>
<DT>
<A NAME="font-editor"><B>Why a font editor, aren't there enough fonts
already?</B></A>
<DD>
<TABLE ALIGN=RIGHT>
<TR>
<TD><BLOCKQUOTE ID="lit">
<SMALL>But Eeyore was saying to himself,<BR>
"This writing business. Pencils<BR>
and whatnot. Over-rated, if you<BR>
ask me. Silly stuff. Nothing in it</SMALL>
<P ALIGN=Right>
<SMALL>Winnie-the-Pooh<BR>
A.A. Milne</SMALL>
</BLOCKQUOTE>
</TD>
</TR>
</TABLE>
<P>
Well... no. Otherwise I wouldn't be writing this, and. more to the point,
there wouldn't be thousands of people downloading it every month.
<P>
I am often asked this question; to me it represents a misapprehension. You
wouldn't go up to a paintbrush maker and ask if he thought there were already
enough watercolor paintings. A font is a work of art and represents the
individual genius of its creator. It is no more redundant than a watercolor.
<P>
However, accepting the question at face value, here are my attempts to answer
it... er, pragmatically.
<OL>
<LI>
There are lots of latin fonts. There are far fewer greek, cyrillic, indic,
thai, chinese, japanese, korean, unicode...
<LI>
There aren't many good quality free fonts available.
<LI>
Researchers into old writing systems often need to design their own fonts
<LI>
Even for latin, traditionally each new style of art and architecture has
an associated style of fonts. New fonts are always being created to reflect
the esthetics of the times.
<LI>
Computer font technology is constantly changing. A font-format that was useful
10 years ago may not be so now.
<LI>
Even if you are satisfied with the fonts that do exist they may not be complete
<UL>
<LI>
Missing ligatures
<LI>
Missing accented glyphs
<LI>
No matching cyrillic or greek glyphs
</UL>
<LI>
Everybody wants a font of his/her own handwriting.
<LI>
Playing with fonts is fun.
</OL>
<P>
FontForge has uses beyond simply creating and modifying fonts. It can convert
from one format to another. It can extract information from the font file.
Or it can simply show you what the font looks like without having to install
it.
<DT>
<A NAME="write"><B>Why did I write it?</B></A>
<DD>
<TABLE Align="Right">
<TR>
<TD><BLOCKQUOTE ID="lit">
Why not?
<P ALIGN=RIGHT>
<SMALL>The Phantom Tollbooth<BR>
Juster</SMALL>
</BLOCKQUOTE>
</TD>
</TR>
</TABLE>
<UL>
<LI>
Because it was fun
<LI>
Because MacroMedia stopped development on Fontographer, and Fontographer
was lacking features that I wanted.
<LI>
To learn
</UL>
<P>
For a more complete description see the
<A HREF="ff-history.html" TARGET="_top">FontForge history</A> page.
<DT>
<A NAME="give"><B>Why do I give it away?</B></A>
<DD>
<UL>
<LI>
Because I approve of free software and hope that the availability of good
products on a good operating system will encourage people not to use proprietary
systems.
<LI>
Because programming is a lot more fun than marketing and giving things away
is easier than selling them.
<LI>
Because I'd have to spend more time doing QA if I sold it (and QA isn't much
fun).
</UL>
<DT>
<B>Why doesn't it use the <A NAME="native">native</A> MS Windows or Mac windowing
system?</B>
<DD>
<UL>
<LI>
FontForge is not a commercial product and is not bound by the constraints
of the market.
<LI>
Doing that port doesn't interest me.
<LI>
I don't have time nor do I have the skill to take that task on.
<LI>
I'd like to encourage people to use Linux/unix
</UL>
<P>
Of course, if I were to use either <A HREF="faq.html#widget-set">gtk or qt</A>
some of the difficulties of porting would vanish. But unfortunately I don't
like either of those widget sets.
<P>
Now... if <EM>you</EM> would like to do the port, that would be wonderful.
I encourage you to do so.
<DT>
<A NAME="widget-set"><B>Why is FontForge based on a non-standard widget
set?</B></A>
<DD>
I wanted a widget set that would handle Unicode reasonably well. In particular
I thought support for bidi text was important for hebrew and arabic typography.
As I was unaware of any widget sets that did that, I wrote my own.<BR>
I also wanted a widget set where I could actually figure out whether the
checkbox was checked or not checked. In far too many cases my eyes can't
work out which is which... (Ironically the most frequent complaint I get
is from people who can't tell whether my checkboxes are checked. I don't
know what to make of that).<BR>
I realize now that that there are essentially two free widget sets that are
far better at unicode support than mine. These are
<A HREF="http://www.trolltech.com/developer/downloads/qt">QT</A> and
<A HREF="http://www.gtk.org/">gtk</A>. I'm still not using either because:
<UL>
<LI>
Converting from one set of widgets to another is tedious. And people send
me bugs which distract me.
<LI>
If I spend my time doing that conversion I won't be making FontForge more
functional.
<LI>
QT is written in C++, and, <A HREF="faq.html#C-plus-plus">as I explain
below</A>, I don't like C++, so that's out.
<LI>
The more I look at gtk the less I like it.
<UL>
<LI>
The support for images is atrocious (which is odd, since it was written for
gimp):
<UL>
<LI>
There is no support whatsoever for client side bitmaps (and I want to support
bitmap fonts)
<LI>
Colors are ordered RGB in color tables for index images, but BGR for 24bit
color images
<LI>
No simple support for transparent images without resorting to full RGBA images,
which is a bit of overkill when I want to draw a simple bitmap.
<LI>
There is no overarching format for images, so I can't have an image which
itself knows whether it's bitmap, index or truecolor.
<LI>
Fixing these was possible, but it involved a lot of very low level work on
my part -- and I only know how to do that work on X.
</UL>
<LI>
I find the file chooser dialog really ugly. And it's so complex I can't figure
out how to modify it to make it look nice (by my standards, that is).
<LI>
I also can't figure out how to modify the file chooser to make it behave
the way the fontforge's file chooser currently behaves (popup windows showing
FontNames as you move the mouse over fontfiles, a pull down list of recently
used files attached to the filename input box, etc.)
<LI>
gtk+2 doesn't run natively on Mac OS, and the only people porting gtk to
the mac seem to be working on gtk-1
<LI>
Many of the widgets I want to use have been deprecated. Sometimes I can't
figure out what replaces them, sometimes I am forced to used a far more complex
widget instead.
<LI>
So I tend to wrestle with it for a while and then decide than my current
widgets are better after all.
<LI>
I did get a limitted version of fontforge running under gtk. I would be greatful
if someone else would choose to extend and maintain it.
</UL>
</UL>
<DT>
<A NAME="C-plus-plus"><B>Why isn't FontForge written in C++ (or <I>Why C++
is not my favorite language</I>)?</B></A>
<DD>
I've been a little surprised to be asked this question, I had not realized
my choice of language needed justification, but it appears to do so...
<P>
Basically because I don't find object-oriented practices helpful in most
cases, because I find C++ far too complex and badly designed, and because
I can't debug it easily.
<UL>
<LI>
I grew up with SIMULA and dabbled with SmallTalk and found after a few years
that there were very few problems where an object oriented approach seemed
natural to me. In most cases it just seemed to impose unneeded complexities
on the problem.
<LI>
The semantics of a C++ program cannot be specified. The compiler is free
to generate temporaries as it wishes. In C this is not a problem, but in
C++ the creation of a temporary can involve calling a constructor and a
destructor which may have untold side-effects. I find this frightening.
<LI>
The order of execution of external constructors is unspecified. I have seen
many inexplicable bugs caused by this
<LI>
I find it extremely difficult to debug C++. Stepping through a statement
often involves many unexpected procedure calls (some of which are inlined
and not obvious). This distracts from my main purpose in debugging.
<LI>
Finally I find the language badly specified and too complex. Its various
concepts do not fit well together. Each compiler seems to do things slightly
differently.
<P>
I first met C++ in about 1981 when it was called C with Classes. I wrote
the C++ front end for Green Hills Software's compiler suite from 1987 to
1994 and I tracked each new version of the language from 1.1 to ANSI.
<P>
Each version added new features which did not sit well with the old ones.
Each version was badly specified. The reference implementation was wildly
different from the specification. For example the behavior of virtual functions
inside constructors was not specified until version 2 of the language and
since this behavior was different from naive expectations this caused bugs.
My favorite confusion occurred in (I think it was) the version 2.1 specification
where on one page, within a few paragraphs, the following two sentences occurred:
"Unions may contain member functions." and "Unions may not contain member
functions.".
</UL>
<P>
The above are my personal opinions based on my experience and explain why
<I>I</I> do not use C++. Your opinions probably differ, few people have spent
5 years writing C++ compilers.
<DT>
<B><A NAME="bsd-license">Why do I release FontForge with the BSD license
and not GPL?</A></B>
<DD>
I just don't like GPL. It's partly prejudice, partly real.
<P>
I don't like forcing restrictions on people.
<P>
I'm giving away fontforge, so I do.
<P>
The <A HREF="license.html" TARGET="_parent">BSD license </A>says "Don't sue
me, and include my copyright notice if you use my code" and that's all I
care about.
<P>
Perhaps I am naif, but I don't believe that anyone is going to start selling
fontforge. Why would they? It makes no sense for someone to try to sell what
I give away freely. If they add functionality to fontforge, then that's a
different matter, but in a sense they aren't charging for fontforge, they
are charging for the code they have added to it. It would be annoying if
someone did that, a bit rude in my eyes, but I'm not going to say "no".
<P>
Now someone might take a small piece of fontforge and use it in something
else. That doesn't bother me. I know that some of my OpenType code has been
snagged by some TeX packages. And I have snagged code for generating checksums
from some other packages.
<P>
I rather like helping other people. And people have helped me.
<DT>
<B><A NAME="libraries">Why does FontForge load libraries at run time rather
than being linked with them?</A></B>
<DD>
I dislike dependencies. The fewer the better.
<P>
I hate when I download a package and discover it won't work unless I download
half a dozen other packages (which, in their turn may demand that I download
yet more packages).
<P>
I want to download a package and just have it work.
<P>
So I try to write as much code myself as I can and release it all together
in a lump and not force people to wander all over the web looking for disparate
parts.
<P>
When I can't figure out how to do something myself I will use an external
library if I must. Even then I will try to insure that fontforge will run
if the library is not present on a system. When I release a binary package
I don't want to have to release 32 packages per host depending on the possible
presence or absence of 5 different libraries. But I also don't want to force
someone to install a library that s/he will never use just to get fontforge
to start.
<P>
If a user will never look at an svg glyph then they don't need to install
libxml2. If the user will never import a jpeg image (and there's really no
reason to want to do that) then they don't need to install libjpeg.
<P>
Instead, the binaries I release will try to load a library dynamically (dlopen)
<EM>when they need it</EM> and not before. This will also speed up starting
fontforge. If the library is on the system then all is happy and nice. If
the library is not, then that functionality is lost -- but the rest of fontforge
continues to work.
<DT>
<B><A NAME="roadmap">Why is there no future roadmap for FontForge?</A></B>
<DD>
<TABLE ALIGN=RIGHT>
<TR>
<TD><BLOCKQUOTE ID="lit">
<B><SMALL>TYSON:</SMALL></B><BR>
I'm not bewildered, I assure you I'm not<BR>
Bewildered. As a matter of fact a plan<BR>
Is almost certainly forming itself in my head<BR>
At this very moment. It may even be adequate.
<P ALIGN=RIGHT>
<I>The Lady's not for Burning</I><BR>
Christopher Fry
</BLOCKQUOTE>
</TD>
</TR>
</TABLE>
<P>
Mostly because I don't thnk that way. I don't plan things out, I have a vague
idea where I want to go and I explore in that direction.
<P>
Consider python scripting. I decided to add python to fontforge. I found
that meant it became easier to design a mechanism so users could create their
own scripts to add import/export file formats. And then startup scripts,
and scripts when certain standard "events" happened. And then I could allow
users to define their own menu items. And then I figured out how to add fontforge
to python (as opposed to the reverse). And now I realize that there is no
reason I couldn't define a set of c-bindings so that people could call fontforge
as a library from within C programs. And who knows where that will lead --
if anywhere.
<P>
Each stage means I can see a little further, and go a little further, and
then see a little more.
<P>
And often ideas will come from users, someone will ask for functionality
I had not thought of.
<P>
I did maintain such a page for a while. I found that half the things I wrote
never happened, and most of the time I didn't bother to update the page.
I'd forget about it. It was dull. Far better to <I>do</I> that to simply
speculate on what I might do were I not speculating.
<P>
So don't ask me what will happen next, because I don't know either. It's
an adventure. We'll just have to wait and see.
<DT>
<A NAME="Pots"><B>Does working on FontForge provide the same kind of pleasure
as working on pots or baking bread?</B></A>
<DD>
<IMG SRC="bowlweb.gif" WIDTH="150" HEIGHT="150" ALIGN="Right"><SMALL><B>From
an interview with <A HREF="http://ospublish.constantvzw.org/?p=221">Open
Source Publishing</A>, done at
<A HREF="http://www.libregraphicsmeeting.org/">LGM</A>2007</B></SMALL><BR>
I like to make things. I like to make things that -- in some strange definition
are beautiful. I'm not sure how that applies to making bread, but my pots
-- I think I make beautiful pots. And I really like the glazing I put onto
them.
<P>
It's harder to say that a font editor is beautiful. But I think the ideas
behind it are beautiful in my mind -- and in some sense <I>I</I> find the
user interface beautiful. I'm not sure that anyone else in the world does,
because it's what I want, but I think it's beautiful.
<P>
And there's a satisfaction in making something -- in making something that's
beautiful.
<P>
And there's a satisfaction too (as far as the bread goes) in making something
I need. I eat my own bread -- that's all the bread I eat.
<P>
So it's just -- I like making beautiful things.
<DT>
<A NAME="legal"><B>Is it legal to modify a font? Is it ethical?</B></A>
<DD>
Many current fonts are based on the work of great designers from centuries
past -- so reusing other people's designs has a long history. On the other
hand, no matter what the law, it is clearly unethical to steal the work of
a living designer.
<P>
Legal matters vary from country to country (and perhaps within countries).
You really should consult a lawyer for a definitive answer. Here are some
guidelines:
<P>
Look at the license agreement you received with the font and see what it
has to say on this issue.
<P>
TrueType (and OpenType and potentially CID-keyed fonts) have a field in the
OS/2 table called FSType which allows the font designer to place restrictions
on what other people can do with the font. If this field prohibits modification
fontforge will ask you to make sure you have an agreement with the font designer
which supersedes this field.
<P>
My understanding of US law (but check with a lawyer before relying on this)
is that:
<UL>
<LI>
There is minimal legal protection for font designs. Ages ago some legal figure
claimed "The alphabet is public." This meant a type design could not be
copyrighted.
<P>
However (I'm told) a designer may register (with the government) for a design
patent which protects the design for 14 years (if granted). I don't believe
it can be renewed, but I may be wrong.
<P>
Registering for a patent is an expensive and time-consuming process and is
often outside the ability of a small design firm. As far as I know the law
has never been tested in the US so the protection may be questionable.
<LI>
Font <EM>programs</EM> (such as a postscript or truetype font file, but not
a bitmap font file) may be copyrighted. This means the design itself is not
protected, but the mechanism for creating it is.
<LI>
Font names may be trademarked.
</UL>
<P>
My understanding is that in the UK:
<UL>
<LI>
There is something called a "design right" which is somewhat like a copyright
and protects a design for 5 years. A designer may also register the design
with the government up to 5 times to extend this protection to 25 years.
</UL>
<P>
Throughout the EU:
<UL>
<LI>
There are EU design rights. I'm not sure about the specifics of these, nor
how they interact with country specific laws (as the British design rights
above).
</UL>
<P>
In Canada:
<UL>
<LI>
Font designs may be registered as "industrial designs" for a limited time
(~15 years)
</UL>
<P>
I would welcome any additions or corrections here, as well as info on the
laws governing fonts in other countries. There is a
<A HREF="http://typophile.com/node/42709">thread on typophile</A> which discusses
this.
<P>
There is a good summary at the
<A href="http://www.fontembeddng.com/fonts-and-the-law">font embedding</A>
website.
<DT>
<A NAME="pointsize"><B>What is a 12 point font?</B></A> <B>(What measurement
of the font determines the point size?)</B>
<DD>
<IMG SRC="pointsize.png" WIDTH="147" HEIGHT="96" ALIGN="Right">A font is
12 points high if the distance between the baselines of two adjacent lines
of (unleaded) text is 12 points.
<P>
The pointsize is not based on the sizes of any of the glyphs of the font.
<P>
Back when fonts were made out of metal, the pointsize of the font was the
height of the metal slugs used for that font.
<P>
In some sense this is not a very good measure of the size of a font (some
fonts may allow more room for accents or ascenders or descenders than others
meaning that the height of the actual glyphs will be smaller).
<P>
There is also a measurement scheme based on the x-height of the glyphs.
<P>
In England and the US a point has traditionally meant the pica point
(1/72.27<SUP>th </SUP>of an inch), while in Europe the point has been the
didot point (1/67.54<SUP>th</SUP> of an inch). The Europeans have a slightly
larger point, but the glyphs of English and European fonts appear the same
size. English does not use accents (except in very rare cases) while most
European languages do, and the slight increase in the size of the point allows
more room for accents.
<P>
(Of course now most Europeans are probably forced to use the pica point by
their desktop software, while most computer fonts now contain accented glyphs,
so the distinction and the reason for it may have vanished).
<DT>
<A NAME="linespace"><B>How do I set the line spacing on a font?</B></A>
<DD>
It depends on the kind of font you are generating, the operating system under
which you are running, and luck.
<UL>
<LI>
For Type1 fonts there is no way to set the line spacing. Applications will
often take the values specified in the font's bounding box and use those
to set the line spacing. This is a really bad idea on their part, but it
is common practice.
<LI>
For True/Open Type fonts the answer is complicated.
<UL>
<LI>
On the mac<BR>
The line spacing is set by the ascender and descender values of the 'hhea'
table. These in turn are set to the bounding box values of the font. Not
a good choice. You can control these values from
<A HREF="fontinfo.html#TTF-Metrics" TARGET="_top">Element->Font
Info->OS/2->Metrics</A>.
<LI>
On windows<BR>
Line spacing is supposed to be set to the Typo Ascent/Typo Desent values
specified in the OS/2 table. And these in turn are supposed to sum to the
emsize. (FontForge sets these values to the ascent/descent values you specify
for your font). Unfortunately most windows applications don't follow this
rule, and instead base linespacing on the Win Ascent/Descent values of the
OS/2 table. These values are supposed to specify a clipping region for the
font (not line spacing). The clipping region should be as big as the font's
bounding box, but in some cases needs to be bigger. Again these may be set
from <A HREF="fontinfo.html#TTF-Metrics" TARGET="_top">Element->Font
Info->OS/2->Metrics</A>.
<P>
(The clipping region should be bigger than the bounding box if a GPOS lookup
could move a glyph so that it extended beyond the bounding box (mark to base
is likely to cause problems). I'm not sure how this applies to cursive
positioning in Urdu where GPOS lookups can make lines arbetrarily tall)
<P>
MicroSoft has added a redundant bit to the OS/2 table, which essentially
tells applications they should follow the standard and use the Typographic
linespacing fields. This bit is called UseTypoMetrics in OpenType, and in
FontForge it is available as Element->Font Info->OS/2
->Metrics->Really Use Typo Metrics.
<LI>
On linux<BR>
I don't know that there is a general consensus. An application will probably
use one of the above methods.
</UL>
</UL>
<P>
Actually this is not a very useful question any more. Modern fonts tend to
have several different scripts in them and the different scripts may have
different line spacing requirements. Even within one script there may be
differences (English uses no (or extremely few) accented letters, while most
other European languages use accents, thus English could be set more densely
than German).
<P>
Instead of having one global measurement which controls the line spacing
for all uses of the font, it is better to have more specific measures which
control the line spacing dependent on conditions. The OpenType
<A HREF="baseline.html" TARGET="_top">'BASE' table </A>does this. It allows
you to specify extent data depending on script, language and active feature
(for example, a 'mkmk' feature might increase the line spacing). I don't
know whether any applications actually make use of these data
<DT>
<A NAME="em-units"><B>How big will my glyphs be?</B></A>
<DD>
Unfortunately this seemingly simple question cannot be answered. Your glyphs
may be any size. Outline glyphs may be scaled and even bitmap glyphs will
be different sizes depending on the screen resolution.
<P>
Suppose instead that you have an outline font that you draw at 12 points.
Then we can answer the question.
<P>
Suppose you have a dash glyph that is 500 internal units long, and the font
has an em-size of 1000 units. Then your glyph will be 500/1000 * 12 = 6points
long. On a 72 dpi screen this will mean the dash is 6 pixels long.
<P>
<B>What are em-units? (internal units?)</B>
<P>
When you create your font you can use
<A HREF="fontinfo.html#PS-General" TARGET="_top">Element->Font
Info->General</A> to provide an em-size for your font. This is the sum
of the typographic ascent and descent (in the days of metal fonts, the height
of the metal slugs, the baseline to baseline distance). Generally the em-size
will be 1000 or 2048. This gives you the number of internal units (also called
em-units) used to represent em.
<P>
Within fontforge outline glyphs are displayed using the coordinate system
established here. See also the
<A HREF="overview.html#em-unit" TARGET="_top">section on em-units in the
overview.</A>
<DT>
<B><A NAME="license">What's a good license to use on an open source
font?</A></B>
<DD>
Many fonts have been released under one of the licenses designed for open
source programs --
<A HREF="http://www.opensource.org/licenses" TARGET="_top">see the Open Source
Initiative list of approved licenses </A>-- but these generally do not meet
the specific needs of font designers. I know of two licenses specifically
produced for fonts:
<UL>
<LI>
<A HREF="http://scripts.sil.org/OFL" TARGET="_top">The Open Font License
from SIL</A> (and its
<A HREF="http://scripts.sil.org/OFL-FAQ_web">FAQ</A>)<BR>
The above is the license I would
recommend.<A HREF="OFL-Unofficial.html" TARGET="_top"><BR>
A collection of unofficial translations of the OFL</A>. These are not legally
binding but may help non-English speakers get the intent of the license.
<LI>
<A HREF="http://www.gnome.org/fonts/#Final_Bitstream_Vera_fonts" TARGET="_top">The
license Bitstream used to release the Vera fonts</A>
</UL>
<P>
The <A HREF="http://www.gnu.org/licenses/gpl.html">GNU General Public License
</A>is also often used.
<DT>
<A NAME="Minimum"><B>Minimum requirements</B></A>
<DD>
This depends heavily on what you want to do. FontForge is mainly limited
by memory (though screen real estate can be a problem too)
<UL>
<LI>
If you are interested in scripts with no more than few hundred simple glyphs
(like the latin alphabet) then 192Mb is more than enough.
<LI>
If you are doing serious editing of CJK fonts then 512Mb is on the low end
of useablity.
</UL>
<P>
FontForge requires a color (or grey-scale) monitor -- black & white will
not suffice.
<DT>
<A NAME="excessive-memory"><B>Why does FontForge use so much memory?</B></A>
<DD>
Fonts are generally stored in a very compact representation. Font formats
are designed to be small and easily rasterized. They are not designed to
be edited.
<P>
When it loads a font FontForge expands it into a more intuitive (well intuitive
to me) format which is much easier to edit. But is much bigger.
<P>
It would probably be possible to rewrite FontForge to use a more efficient
memory representation. But this would be an enormous amount of work and doesn't
interest me.
<P>
Sfd files are large because they are an ASCII representation of this same
expanded format. They weren't designed to be compact but to be legible.
<P>
See also: <A HREF="#memory">My system keeps crashing because FontForge keeps
running out of memory. What can I do about it?</A>
<DT>
<A NAME="font-install"><B>How do I install the fonts once I've made
them?</B></A>
<DD>
Well it rather depends on what system you are working on, and what type of
font you've got:
<DL>
<DT>
<STRONG>Unix & <A NAME="X-Install">X</A></STRONG>
<DD>
<DL>
<DT>
Outline fonts and fontconfig
<DD>
Many programs now use fontconfig to find fonts (including fontforge). To
install a font for fontconfig, simply copy the file into your ~/.fonts directory.
<DT>
Bitmap fonts, and vanilla X11 installs
<DD>
I'd suggest that you look at the
<A TARGET="_top" HREF="http://www.linuxdoc.org/HOWTO/Font-HOWTO.html">linux
font HOWTO file</A>, and the
<A TARGET="_top" HREF="http://www.linuxdoc.org/HOWTO/mini/FDU/">font
deuglification HOWTO</A> as good starting points. But I'll run over the
highlights
<P>
Essentially you designate one (or several) directories as a "font directory".
You move your fonts to that directory. You build up certain data structures
that X needs, and you tell X to include this directory in your font path.
Sadly different versions of X and the X font server use slightly different
conventions. You may need to alter these procedures a bit.
<P>
For example, if you want to install a <EM>bdf font </EM>called frabnuts-13.bdf
then you might:
<BLOCKQUOTE>
<PRE>$ mkdir my_fonts
$ mv frabnuts-13.bdf my_fonts
$ cd my_fonts
$ bdftopcf frabnuts-13.bdf >frabnuts-13.pcf
$ mkfontdir
$ xset fp+ `pwd`
</PRE>
</BLOCKQUOTE>
<P>
and your fonts should be installed. After that, whenever you start X you
need to remind it of where your fonts live, so you should add<BR>
<CODE> $ xset fp+ /home/me/my_fonts</CODE><BR>
to your .xsession (or equivalent).
<P>
If you want to install <EM>postscript fonts</EM><BR>
You should generate them as postscript binary (.pfb) files, then move both
the .pfb and the .afm file into (one of) your font directory(ies) and run
<A TARGET="_top" HREF="http://rpmfind.net/linux/rpm2html/search.php?query=type1inst">type1inst</A>
in it.<BR>
type1inst will probably complain that your font doesn't have a foundry and
will probably get the encoding wrong. You can either:
<UL>
<LI>
Ignore it and nothing bad will happen
<LI>
Manually edit fonts.scale after running type1inst to fix these entries
<LI>
Make your font's Copyright be reasonable, and then edit type1inst and add
your foundry (directions for this are in type1inst itself)
</UL>
<P>
If you want to install <EM>truetype fonts</EM><BR>
You move the .ttf file into your font directory and run mkttfdir and
mkfontdir.<BR>
(<A TARGET="_top" HREF="http://rpmfind.net/linux/rpm2html/search.php?query=mkttfdir">mkttfdir</A>
has a small problem with fonts created by FontForge, it will almost invariably
complain that it doesn't recognize the foundry. You can safely ignore this,
but if it bothers you then add a line to ttmkfdir.c at 936<BR>
<CODE> { "PFED", "FontForge"
},</CODE>
<P>
Some versions of X (ie, those shipped by redhat) rely on the x font server
to do font work rather than the X server itself. You may need to use chkfontpath
to add your new directory to the font server's font path (rather than xset
fp).<BR>
You may also need to insure that the font directory (and all its parent
directories) are readable to world. (the font server runs as a non-privileged
user)
<P>
I haven't seen anything that says X supports <EM>opentype</EM> fonts yet,
but since freetype does (and I think X's rasterizer uses freetype) then X
might support them too. Installing them will require manual editing of
fonts.scale though (mkttfdir uses freetype1 which doesn't support otf files).
<P>
That sounds really confusing. I apologize, I'm not a good writer and there
are too many choices in configuring X...
<DT>
<STRONG>KDE</STRONG>
<DD>
(I don't know KDE very well, so take my experience with a grain of salt)
Under KDE there is a tool called
<A TARGET="_top" HREF="http://www.cpdrummond.uklinux.net/kfontinst/">kfontinst</A>
which is supposed to do all the configuration work for you. I was only able
to get it to work as root and had to reconfigure my system to follow its
conventions, but once that was done it installed X fonts quite handily. I
never did figure out how to get it to install ghostview fonts. (I experimented
with version 0.9.2)
</DL>
<DT>
<STRONG>TeX</STRONG>
<DD>
TeX has its own (platform independent) system for installing fonts. I've
described my experiences so far
<A HREF="PfaEdit-TeX.html#TeX-Install" TARGET="_top">elsewhere in this
document</A>.
<DT>
<STRONG><A NAME="Windows-Install">Windows</A></STRONG>
<DD>
You install truetype fonts on windows by dropping them into the \Windows\Fonts
directory on your machine. You may need to set the execute permission bit
on the font before installing it.<BR>
<FONT COLOR="Red"><STRONG>Do <BIG>NOT</BIG> generate the font directly into
\Windows\Fonts</STRONG></FONT>, this doesn't seem to work (at least on under
my XP machine). You must generate the font into another directory and drag
& drop it to \Windows\Fonts .<BR>
If you want to use type1 fonts you will need to install adobe type manager
and follow its instructions.<BR>
If you want to install opentype fonts then on old systems (before windows
2000, I think) you need to install ATM, on more recent systems opentype should
work the same way truetype does.
<DT>
<STRONG><A NAME="OS9-Install">Macintosh OS 9</A></STRONG>
<DD>
Oh dear. The mac sticks fonts into resource forks and wraps them up in its
own headers. Mac fonts aren't compatible with anybody else's. FontForge can
create a resource fork if it wraps the font up in a macbinary encoding. See
the <A HREF="faq.html#How-mac">following question</A> for more information.<BR>
I've also written <A TARGET="_top" HREF="http://fondu.sourceforge.net/">some
utilities </A>designed to convert from one format to another and they may
prove useful.<BR>
<A TARGET="_top" HREF="http://babel.uoregon.edu/yamada/fontconversionfaq.html">University
of Oregon has some links that might be helpful</A>.<BR>
Once you've converted your fonts you just drop them into the System Folder
and they should be available after that.
<DT>
<STRONG><A NAME="OSX-Install">Macintosh OS X</A></STRONG>
<DD>
On OS/X fonts should be placed either in the top-level Library/Fonts directory
(By default <CODE>/Mac OS X/Library/Fonts/</CODE>), in the System/Library/Fonts
directory, or in the user's appropriate fonts sub-directory
(<CODE>~/Library/Fonts</CODE>).<BR>
Either a resource font (unwrapped from its macbinary wrapper) or a dfont
may be used. You can also use straight ttf and otf files (ie. the same file
you might use on Unix or MS).<BR>
As far as I can tell the old NFNT bitmap resources do not work on my OS 10.2.
If you want to use bitmap fonts wrap them up in a ttf file or an sfnt. However
if you want to use a Type1 resource font, you must generate a (useless) bitmap
font and install them both.
</DL>
<DT>
<A NAME="Bad-Windows-Install"><B>Why won't FontForge's fonts install on some
MS Windows machines?</B></A>
<DD>
Do <FONT COLOR="Red"><STRONG>NOT</STRONG></FONT> generate a font directly
into the \windows\fonts directory. Generate the font into a different directory
and then use windows drag and drop to install the font. (Windows appears
to do magic when it moves the font into that directory).
<P>
Recently (2009) a windows security patch decided that fonts with a 'name'
table bigger than 5K were insecure and refused to install them. Frequently
this is caused by having the full text of a license included in the font.
<P>
I am told that fonts produced by old versions of FontForge will not install
on Windows 2000 (and XP) systems.
<P>
I believe this problem is fixed now (as of 20-Oct-2003). If you have an older
version please upgrade.<BR>
If you are copying a font from another machine make sure the execute bit
is set in the permissions of the font file (I don't know how to do this with
the Windows UI, under cygwin you say <CODE>$ chmod +x foo.ttf</CODE>
<DT>
<A NAME="How-mac"><B>How do I edit fonts from my macintoy?</B></A>
<DD>
<DL>
<DT>
Mac OS/9 (or less)
<DD>
Traditionally the macintosh has stored fonts in the resource fork of files
(after about OS/8.5 I believe the mac also supported bare .ttf files). This
causes problems for any machine other than a mac, because the very concept
of a resource fork is lacking.<BR>
There are several programs whose job it is to store all of a macintosh file
in one package that can be manipulated on other systems (mac binary and binhex
are the most common). FontForge knows how to read both of these formats and
can extract a postscript or truetype font from either. FontForge can also
create fonts in macbinary format (I see no reason to support both output
formats, and macbinary is slightly simpler).<BR>
So to edit a font on your mac:
<OL>
<LI>
Find the file in the <TT>System Folder:Fonts</TT> folder
<LI>
Copy the file over to your unix machine
<UL>
<LI>
Use Fetch and specify macbinary format
<LI>
Or use some tool like binhex which can create the file directly
</UL>
<LI>
Open it in FontForge
<LI>
Edit it
<LI>
Save it back in macbinary format
<LI>
Copy it back to your mac
<UL>
<LI>
Fetch will automatically undo the macbinary wrappers and make it be correct
<LI>
Or various other tools can unwrap it.
</UL>
<LI>
Drop it back into your system folder (where it is automagically moved to
Fonts)
</OL>
<P>
<STRONG>Note:</STRONG> make sure you either replace the original font files,
or that you rename the font within fontforge and (for postscript fonts) that
you give it a new unique id. See the <A TARGET="_top" HREF="fontinfo.html">Font
Info</A> dlg.
<P>
<STRONG>Caveat:</STRONG> A postscript font is useless on a macintosh unless
it is accompanied by at least one bitmap font. If you generate a postscript
font make sure you also generate an NFNT as well (this has the FOND).<BR>
<STRONG>Caveat:</STRONG> The mac is picky about the filename used to contain
a postscript file. It is based on the postscript font name but suffers a
transformation. Don't try to rename this file. Basically the rules are (see
<A TARGET="_top" HREF="http://partners.adobe.com/asn/developer/pdfs/tn/0091.Mac_Fond.pdf">Adobe
Technical Note 0091</A>):
<UL>
<LI>
The fontname is broken into chunks where each chunk starts with a capital
letter.
<LI>
The first chunk may have four lower case letters following the initial capital
<LI>
Subsequent chunks may only have two lower case letters following the capital.
<LI>
Non-letter glyphs (or at least hyphens) vanish.<BR>
So TimesBold => TimesBol, Helvetica-BoldItalic => HelveBolIta,
NCenturySchoolbook => NCenSch
</UL>
<DT>
Mac OS/X
<DD>
On Mac OS/X you can run <A TARGET="_top" HREF="running.html#mac">FontForge
directly</A> (if you've got <A HREF="mac-install.html#Before">X11
installed</A>). OS/X has several font formats, some fonts are stored in the
old format (see above), while others are stored as data fork resources. The
data fork font files generally have the extension ".dfont". On a Mac FontForge
is able to edit both formats directly. OS/X also supports normal .otf and
.ttf font files.
<P>
Mac OS/X does not seem to support the old NFNT bitmap format, but it still
requires that a bitmap font in NFNT format be present before it will use
a resource-based postscript font. (It is probably not the NFNT resource which
is required, but the FOND which goes along with it. But I'm not going to
write something to produce a bare FOND resource -- nothing else does either).
</DL>
<DT>
<B><A NAME="How-family">How do I create a mac font family? (How do I get
the mac to group my fonts so that the italic and bold styles work)?</A></B>
<DD>
I am told that in 10.6 the prefered method of grouping fonts is to use ttc
files, prior to 10.6 ttc files didn't work (well) and the prefered method
was to produce mac font families.
<DL>
<DT>
Snow Leopard (10.6) and after
<DD>
First open all the fonts that make up your family in fontforge.<BR/>
Then choose <CODE>File->Generate TTC</CODE><BR/>
This should be simpler than the old method.
<DT>
Leopard (10.5) and before
<DD>
For the Style menu in most mac applications to work on your fonts, you must
create a font family. You do this with the
<A TARGET="_top" HREF="filemenu.html#GenerateMac">File->Generate Mac
Family</A> command.
<P>
All the fonts in a family must have the same Family name (See the
<A TARGET="_top" HREF="fontinfo.html">font info</A> dialog). Font Families
are handled rather differently under Carbon (the old font handling mechanism
used in OS 9) and under ATSUI (on OS/X).
<P>
Under Carbon, the font family is limited by the design of the Mac 'FOND'
resource, which reflects the computer font technology of the early 1980s.
Modern computer fonts often have variants that can't be expressed in it.
FONDs support any combination (except one containing both Extend and Condense)
of the following styles:
<UL>
<LI>
Bold
<LI>
Italic
<LI>
Condense
<LI>
Extend
<LI>
Underline
<LI>
Shadow
<LI>
Outline
</UL>
<P>
Mac FONDS do not support "Black", "DemiBold", "Light", "Thin" or
"Extra-Condensed" variants.
<P>
Under ATSUI, on the other hand, a family seems to consist of all fonts in
a given resources file which have the same FamilyName.
<P>
In order that a family be useful under both systems, Apple appears to place
several FONDs inside such a font file. Each FOND contains a sub-family of
related fonts. The 'FOND's appear to be distributed as follows:
<P>
Suppose you have a family of fonts with the following styles:<BR>
Regular, Bold, Italic, Bold-Italic, Condense, Condense-Italic, Oblique, Light,
Light-Italic, Black<BR>
Then you should create a font family with the styles that the FOND does support,
which in this case would be<BR>
Regular, Bold, Italic, Bold-Italic, Condense, Condense-Italic<BR>
For each of these use
<A HREF="fontinfo.html#FONDName" TARGET="_top">Element->Font
Info->Mac</A> to set the FondName field to the font's family name.
<P>
Change the fondname of the other styles, so that the Oblique style has Oblique
in the fond name, the two Light styles have Light in the fond name, and so
on. Set the <A HREF="fontinfo.html#Mac-Style" TARGET="_top">Mac Style</A>
on the "Light" variant of the font to be Regular (everything unselected)
and set the style of the "Light-Italic" variant to be "Italic" -- that is,
forget about the "Light", the FOND can't handle it, that's why we moved it
into its own FOND.
<P>
Having done this setup, the <A HREF="filemenu.html#GenerateMac">Generate
Mac Family </A>command should be able to put all the fonts into appropriate
FONDs, and then place all the FONDs into one file, which the Mac should interpret
correctly.
</DL>
<DT>
<B><A NAME="Mac-ATM">Why doesn't ATM work on my (mac) fonts?</A></B>
<DD>
Insure that the font has an encoding of Macintosh Latin when you generate
it.
<P>
This is really a limitation on ATM's part and there's nothing FontForge can
do about it.
<P>
If you generate a font with an encoding other than Macintosh Latin, then
the Mac's default behavior is to force the postscript font to have a Macintosh
Latin encoding. There is a mechanism to turn this behavior off, but if it
is turned off then ATM won't work at all.
<DT>
<B>How do I edit fonts on MS <A NAME="windows">windows</A>?</B>
<DD>
See the <A HREF="ms-install.html">MS Windows install instructions</A>.
<DT>
<B><A NAME="Bad-Windows-Fonts">Why don't my fonts work on windows?</A></B>
<DD>
Here's one possibility: Windows sometimes (and I don't know when) insists
on having a name for the font in the appropriate language (ie. a Japanese
entry for a SJIS font). Try going to
<A TARGET="_top" HREF="fontinfo.html#TTF-Names">Element->Font Info->TTF
Names </A>and adding a set of strings for your language.
<P>
Another possibility is discussed
<A HREF="faq.html#Bad-Windows-Install">here</A>.
<DT>
<A NAME="Missing-Refs"><B>When I load an otf or a type1 font most of my
references have been replaced by inline copies. How do I get my references
back?</B></A>
<DD>
It is very difficult to figure out old references when loading postscript
fonts. Instead FontForge has a special command,
<A HREF="editmenu.html#ReplaceRef" TARGET="_top">Edit->Replace With
Reference</A>, that will search for potential reference candidates in the
font and replace them with references.
<DT>
<B><A NAME="kern-info">Does FontForge read in the old kerning information
from fonts?</A></B>
<DD>
This question needs to be broken down into cases:
<DL>
<DT>
<B>TrueType and OpenType fonts</B>
<DD>
Yes. The kerning information is stored in either the 'kern' or 'GPOS' tables
of these fonts and FontForge can read them (Apple has made a number of extensions
beyond the original truetype spec, FontForge can read these too).
<DT>
<B>PostScript Type1 fonts anywhere other than the Mac.</B>
<DD>
The kerning information is not stored in a Type 1 font file. Instead it is
stored in a file with the same filename as the font file but with the extension
".afm". When FontForge reads a PostScript font it will check for an associated
afm file, and if found will read the kerning information from it.
<DT>
<B>PostScript Type1 fonts on the Mac.</B>
<DD>
No. Again the kerning information is not stored in the font file (it is stored
in a bitmap font file), but on the mac it is impossible to guess what name
to use for the associated bitmap file, and FontForge does not even try. <BR>
See the info below on how to load kerning from a
<A HREF="faq.html#FOND-kern">FOND</A>.
<DT>
<B>AFM and TFM files.</B>
<DD>
FontForge can read kerning information directly from these files and apply
those data to a font. See the
<A TARGET="_top" HREF="filemenu.html#Merge-feature">File->Merge Feature
Info</A> menu command.
<DT>
<B>Mac resource files containing FOND resources.</B>
<DD>
The mac stored kerning information in the <A NAME="FOND-kern">FOND</A> resource
associated with a bitmap font (it is not stored in the file with the postscript
font). If you wish kerning data for a mac postscript font, you must find
a font file containing a bitmap font with the same family and style as the
postscript. FontForge can read kerning information directly from these files
and apply those data to a font. See the
<A TARGET="_top" HREF="filemenu.html#Merge-feature">File->Merge Feature
Info</A> menu command.
<DT>
<B>Adobe Feature files</B>
<DD>
Adobe has a textual representation for OpenType features and lookups, and
fontforge can read these files with the
<A TARGET="_top" HREF="filemenu.html#Merge-feature">File->Merge Feature
Info</A> menu command.
</DL>
<DT>
<B><A NAME="outline-conversion">How do I convert from one outline format
to another?</A></B>
<DD>
The simple answer that will work if you want something quick is:
<OL>
<LI>
File->Open
<UL>
<LI>
an existing font
</UL>
<LI>
<A HREF="generate.html" TARGET="_top">Element->Generate Fonts </A>
<UL>
<LI>
to generate the desired output.
</UL>
</OL>
<P>
If you are converting from one PostScript format to another (pfb to otf,
for example) that's all you need to do. If you are converting between PostScript
and TrueType, you can improve matters if you do a little more work.
<P>
Converting from TrueType (quadratic splines, ttf files) to PostScript (cubic
splines, otf and pfb files):
<OL>
<LI>
File->Open
<UL>
<LI>
(the truetype font)
</UL>
<LI>
<A HREF="fontinfo.html#Layers" TARGET="_top">Element->Font
Info->Layers</A>
<UL>
<LI>
Check <*> All layers cubic
<LI>
[OK]
</UL>
<LI>
Edit->Select->Select All
<LI>
<A HREF="elementmenu.html#Simplify" TARGET="_top">Element->Simplify->Simplify</A>
<LI>
<A HREF="hintsmenu.html#AutoHint" TARGET="_top">Hints->Auto Hint</A>
<LI>
<A HREF="generate.html" TARGET="_top">Element->Generate Fonts </A>
</OL>
<P>
Converting from PostScript (cubic splines, otf and pfb files) to TrueType
(quadratic splines, ttf files):
<OL>
<LI>
File->Open
<LI>
<A HREF="fontinfo.html#Layers" TARGET="_top">Element->Font
Info->Layers</A>
<UL>
<LI>
Check <*> All layers quadratic
<LI>
[OK]
</UL>
<LI>
Edit->Select->Select All
<LI>
<A HREF="hintsmenu.html#AutoInstr" TARGET="_top">Hints->AutoInstr</A>
<LI>
<A HREF="generate.html" TARGET="_top">Element->Generate Fonts </A>
</OL>
<DT>
<B><A NAME="bitmap-conversion">How do I convert from one bitmap format to
another?</A></B>
<DD>
This is also easy, open a bitmap font, and then use
<A HREF="generate.html" TARGET="_top">Element->Generate Fonts</A> to generate
the desired output.
<DT>
<B><A NAME="outline-bitmap">How do I convert from an outline format to a
bitmap format?</A></B>
<DD>
Load the outline font. Then use
<A HREF="elementmenu.html#Bitmaps" TARGET="_top">Element->Bitmaps
Available</A> to generate bitmap strike(s) of the appropriate size(s). This
process is called rasterization, at small pixel sizes it is difficult for
a computer to do well. You might be advised to examine the results of the
rasterization in the <A HREF="bitmapview.html" TARGET="_top">bitmap window</A>
(with <A HREF="windowmenu.html#Bitmap" TARGET="_top">Window->Open Bitmap
Window</A>), and possibly fixup the bitmap as you go. Then when done select
<A HREF="generate.html" TARGET="_top">Element->Generate Fonts</A>, turn
off outline font generation (unless you also want an outline font, of course),
and select the desired bitmap format.
<DT>
<B><A NAME="bitmap-outline">How do I convert from a bitmap format to an outline
format?</A></B>
<DD>
Unless you have a very large bitmap font (such as a TeX font) the following
procedure will not produce good results.
<UL>
<LI>
Before you do anything else make sure you have either the
<A HREF="autotrace.html" TARGET="_top">potrace or autotrace programs
</A>installed on your system
<HR>
<LI>
Create a new font
<LI>
Use the <A HREF="filemenu.html#Import" TARGET="_top">File->Import
</A>command to import your bitmap font into this new font
<UL>
<LI>
Be sure to check the <CODE>[] Into Background</CODE> checkbox
</UL>
<LI>
Edit->Select->Select All
<LI>
Element->Autotrace
<LI>
Element->Add Extrema
<LI>
Element->Simplify<BR>
At this point you will probably want to look at your outline glyphs and clean
them up.
<LI>
File->Generate Fonts
</UL>
<DT>
<A NAME="AAT2OT"><B>Converting from Apple's Advanced Typography to
OpenType</B></A>
<DD>
There are a number of similarities between the results achieved by these
formats, but the overlap is not total. Most conversions will lose some
information.<BR>
The simple answer is that this is pretty much automatic. You load an apple
font, and then Generate an equivalent font with the [*] OpenType checkbox
checked in the Options dialog.<BR>
FontForge will convert any non-contextual features where Apple's feature/setting
matches an OpenType feature. (This includes non-contextual ligatures even
though they live in a contextual format). For more information see the section
on this <A HREF="gposgsub.html#Conversion" TARGET="_top">interconversion</A>.
<DT>
<B><A NAME="OT2AAT">Converting from OpenType to AAT</A></B>
<DD>
Again this is mostly automatic. Load an OpenType font, and Generate an equivalent
font with the [*] Apple checkbox checked in the Options dialog.<BR>
FontForge is capable of converting some contextual OpenType tables to AAT.
Non-contextual features which match an Apple feature/setting will be converted
too. For more information see the section on this
<A HREF="gposgsub.html#Conversion" TARGET="_top">interconversion</A>.
<DT>
<A NAME="hint-subs"><B>How do I make FontForge use hint substitution?</B></A>
<DD>
It happens automagically. <BR>
Or you can control the place where hint sets change by selecting a point
and choosing <A HREF="getinfo.html#HintMask" TARGET="_top">Element->Get
Info</A>->Hint Mask.
<DT>
<A NAME="flex-hints"><B>How do I make FontForge use flex hints?</B></A>
<DD>
It happens automagically. FontForge will generate flex hints in situations
where it is appropriate to do so. You don't need to do anything. If flex
hints are used then the necessary subroutines will be added to the font.
If they are not needed then the subroutines will not be added.
<DT>
<B><A NAME="flex2">How can I tell if it is going to use flex hints?</A></B>
<DD>
If you want to see whether FontForge is going to use flex hints, turn on
the <A HREF="prefs.html#UpdateFlex">UpdateFlex</A> preference item and open
a view on the glyph. FontForge displays a green halo around the center point
of a flex hint.
<DT>
<A NAME="fuzzy"><B>My glyphs are all perfectly hinted, why do some stems
have different widths (or appear fuzzy, or fade away completely)?</B></A>
<DD>
Both PostScript and TrueType require that glyphs be drawn in a clockwise
fashion. Some rasterizers don't care. But other rasterizers will have
difficulties with counter-clockwise paths and produced stems of different
widths when they should be the same, or fuzzy stems, or even nothing at all.
The solution to this is to run Element->Correct Direction on all your
glyphs before generating a font.<BR>
But sometimes the poor rasterizer just can't do the right thing...
<DT>
<A NAME="mensis"><B>How do I set a particular bit in the OS/2 table (or any
other)?</B></A>
<DD>
FontForge does not do this, but I have written a companion program,
<A HREF="http://mensis.sf.net/">mensis</A> (Latin for: "to or for, by, with
or from tables") which gives you bit access to tables. It provides both UI
and scripting access.
<DT>
<A NAME="sfd"><B>What's an sfd file?</B></A>
<DD>
This is FontForge's own format. It a text file, which means it is large but
readable to a human (OK, by a determined human). It only uses ASCII characters
which means it should not be distorted by old mail programs if sent around
the internet (it's a registered MIME type
<CODE>application/vnd.font-fontforge-sfd</CODE>).<BR/>
<A HREF="sfdformat.html" TARGET="_top">An overview of the format.</A>
<DT>
<A NAME="background"><B>FontForge's grey background distresses me. How do
I change it?</B></A>
<DD>
The general mechanism is discussed on the <A HREF="xres.html" TARGET="_top">X
Resources page</A>.<BR>
<A HREF="fontforge-themes.html" TARGET="_top">Here are some combinations
you might try</A>.
<DT>
<A NAME="fontsize"><B>The fonts FontForge uses in its GUI are too small (too
big) how do I change them?</B></A>
<DD>
The X server does not have a good idea about screen resolution, and when
fontforge asks it, the answer is often wrong. The result is that ff may use
fonts that are too small (potentially too big too, but no one has complained
about that one yet). You can tell fontforge the true screen size by adding
a line like
<BLOCKQUOTE>
<PRE>Gdraw.ScreenWidthInches: 14.7
Gdraw.ScreenWidthCentimeters: 37.3
</PRE>
</BLOCKQUOTE>
<P>
to your <CODE>~/.Xdefaults</CODE> file (The general mechanism is discussed
on the <A HREF="xres.html" TARGET="_top">X Resources page</A>). If the GUI
fonts are still too small you can lie about the screen size. If you claim
the screen is smaller (in inches or centimeters) than it actually is, ff
will use a bigger font.
<DT>
<B><A NAME="monospace">How do I mark a font as monospaced?</A></B>
<DD>
You don't. Just insure that all the glyphs in the font have the same width
and then FontForge will automatically mark it as monospaced for you. (If
you mark it as monospaced incorrectly some rasterizers will give strange
results).<BR>
If you want to set a font's panose values yourself
(<A HREF="fontinfo.html#Panose" TARGET="_top">Element->Font
Info->OS/2->Panose</A>) then set the Proportion field to Monospaced.
This is necessary but not sufficient to mark the font as a whole as monospaced.
<P>
If you are unsure whether all the glyphs in your font have the same advance
width use <A HREF="problems.html#Advance">Element->Find
Problems->Random->Check Advance.</A>
<P>
When I say "all glyphs" I really mean <EM>all</EM> glyphs. Even glyphs which
unicode says should be 0 width must have the same width as everything else.
MicroSoft suggests that GPOS be used to do accent combination (etc.) and
then change the advance width on any marks (accents) to be 0.
<DT>
<A NAME="new-encoding"><B>How I do tell fontforge about a new
encoding</B></A>
<DD>
First ask yourself if you really need a new encoding? If you are using OpenType
or TrueType fonts you can usually get by with the standard unicode encoding.
But if you really need a new one here is a rough idea of what to do:
<P>
Figure out what your encoding looks like. Often this will involve searching
around the web to find an example of that encoding. For instance if you want
a devanagari encoding you might look at
<A TARGET="_top" HREF="http://www.cwi.nl/~dik/english/codes/indic.html">a
site which shows the ISCII encodings</A>
<P>
These encodings only show the top 96 characters, presumably the others are
the same as US ASCII. Look at the images and figure out how they map to unicode
(or more precisely what the appropriate postscript names are for those
characters).
<P>
Create a file (call it "Devanagari.ps" in this case). It should start with
a line:
<BLOCKQUOTE>
<PRE>/Devanagari {
</PRE>
</BLOCKQUOTE>
<P>
This tells FontForge that the encoding is called "Devanagari", then follow
this with a list of all the character names (preceded by a slash). We start
with ASCII which starts with 32 .notdef characters, then space, etc.
<BLOCKQUOTE>
<PRE>/Devanagari {
/.notdef
/.notdef
...
/.notdef
/space
/exclam
/quotedbl
...
/braceright
/asciitilde
/.notdef
...
/.notdef
/uni0901
/uni0902
...
/uni096F
}
</PRE>
</BLOCKQUOTE>
<P>
Now load this file into FontForge's list of encodings with Encoding->Load
Encoding, and then apply it to whatever fonts you want.
<DT>
<A NAME="new-name"><B>How do I add a glyph with a new name?</B></A>
<DD>
Let's say you wanted to add a "dotlessi" glyph to an ISO-8859-1 font (this
encoding does not include dotlessi). There are two ways to approach the problem:
<OL>
<LI>
Bring up <CODE>Encoding->Add Encoding Slots...</CODE><BR>
Type in the number of extra glyphs you want (probably 1)<BR>
Press <CODE>OK</CODE><BR>
Scroll down to the end of the font and find the new slot<BR>
Select it<BR>
Bring up <CODE>Element->Glyph Info</CODE><BR>
Type your new name into the <CODE>Unicode Name</CODE> field (in this example
you'd type in <CODE>dotlessi</CODE>)<BR>
Press the <CODE>Set From Name</CODE> button<BR>
Press <CODE>OK</CODE><BR>
Now draw a dotlessi in the glyph.
<LI>
Bring up <CODE>Encoding->Reencode->ISO-10646-1</CODE><BR>
Bring up <CODE>View->Goto</CODE><BR>
Type in <CODE>dotlessi</CODE><BR>
Press <CODE>OK</CODE><BR>
Now draw the dotlessi glyph in the selected glyph slot<BR>
Bring up <CODE>Encoding->Reencode </CODE>again<BR>
Change the encoding back to whatever it was
</OL>
<DT>
<A NAME="glyphnames"><B>Why does FontForge give some of my glyphs the wrong
name?</B></A>
<DD>
FontForge's naming conventions are those specified in
<A HREF="http://partners.adobe.com/public/developer/opentype/index_glyph.html">Adobe's
glyph naming conventions</A>, and, unfortunately, there are some problems
here (generally for compatibility with old encodings). I am aware of the
following issues:
<DL>
<DT>
Delta
<DD>
is assigned to U+2206, "INCREMENT" rather than U+0394, "GREEK CAPITAL LETTER
DELTA", probably because Increment was part of the old MacRoman encoding.
<DT>
Omega
<DD>
is assigned to U+2126, "OHM SIGN", rather than U+03A9, "GREEK CAPITAL LETTER
OMEGA".
<DT>
mu
<DD>
is assigned to U+00B5, "MICRO SIGN", rather than U+03BC, "GREEK SMALL LETTER
MU", probably because Micro Sign was part of ISO-Latin1 and MacRoman
<DT>
omega1
<DD>
Unicode calls this glyph "GREEK PI SYMBOL". It looks like an omega though.
<DT>
Tcommaaccent, tcommaaccent
<DD>
are assigned to U+0162,U+0163 "LATIN CAPITAL/SMALL LETTER T WITH CEDILLA",
rather than U+021A,U+021B "LATIN CAPITAL/SMALL LETTER T WITH COMMA BELOW",
probably because of a confusion in the early Unicode spec.
<DT>
dotlessj
<DD>
is assigned to U+F6BE (in the private use area) rather than U+0237 "LATIN
SMALL LETTER DOTLESS J", because Adobe saw the need for a dotlessj glyph
before Unicode did and assigned a slot in the private use area. Then in 4.1
Unicode added the glyph to the standard.
</DL>
<DT>
<B><A NAME="non-integral">Is it safe to use non-integral coordinates?</A></B>
<DD>
FontForge allows you to edit with non-integral coordinates. Many font editors
don't and some have wondered if the use of non-integral coordinates will
it distort their fonts when they are rasterized?
<P>
The answer depends on the font format and how you save the font.
<P>
TrueType fonts can only express integral coordinates. When FontForge creates
a TrueType font it will round all coordinates to integers. This rounding
will introduce a slight distortion in the curve.
<P>
PostScript (type1, PostScript OpenType, type2, etc.) fonts can express
non-integral coordinates in the font format -- but it takes a lot more space
in the font file. Type1 fonts tend to take more space to express this than
type2 (opentype) fonts. By default FontForge will round to int on these as
well, BUT you can change that in the Generate Options dialog.
<P>
If your font is rounded then there will be some distortion. If it is not
rounded there should be no distortion. In PostScript fonts it should be safe
to use non-integral coordinates provided you turn off rounding when you generate
the font. The font file will be bigger, but more accurate.
<P>
If you feel you need more accuracy in TrueType you can change the em-size
to 8096.
<P>
You can do this on PostScript Type1 fonts too, however, there are some
applications which assume that all OpenType postscript fonts have an em-size
of 1000, so it is best not to do this for OpenType output.
<DT>
<A NAME="Open-size"><B>Why isn't my Open Type font much smaller than the
.pfb file?</B></A>
<DD>
This is probably because you didn't round to int before saving the font.
FontForge will save the font using fixed point numbers which take up a lot
more space than normal integers.
<DT>
<A NAME="Open-difference"><B>What's the difference between OpenType and
PostScript (or TrueType) fonts?</B></A>
<DD>
Both PostScript and TrueType define a file format and a glyph format. OpenType
uses the TrueType file format with a PostScript glyph format (actually OpenType
includes the TrueType glyph format as well, but the OpenType definition says
such fonts should still be called TrueType fonts so I ignore that aspect).
<P>
The PostScript used in OpenType is slightly different from that used in .pfa
and .pfb files. pfa/b files are Type1 fonts while OpenType uses Type2 fonts.
Type2 is almost a superset of Type1 with a few minor changes and many extensions.
Adobe's subroutine based extensions to Type1 (flex hints, hint substitution,
counter hints) have been added to Type2 as direct instructions.<BR>
OpenType can also include additional information (see
<A HREF="#AAT-Open">below</A>) that allows for the layout of complex scripts
(Arabic, Indic, etc.) as when as support for glyph variants and other aspects
of fine typography.
<DT>
<A NAME="AAT-Open"><B>What is the difference between AAT (Apple Advanced
Typography) and OpenType?</B></A>
<DD>
Both of these are extensions to the basic TrueType font which can contain
information for laying out complex scripts (like Arabic or Indic scripts)
as well as support for glyph variants and other aspects of fine typography.
They use totally different internal formats for the more complex aspects
of this task, formats which have different expressive powers so that neither
format can be converted to the other without the possibility for some loss
of information. I discuss this in greater detail
<UL>
<LI>
<A HREF="editexample6-5.html#Conditional">In the tutorial</A>
<LI>
<A HREF="gposgsub.html" TARGET="_top">In the section on advanced typography</A>
</UL>
<DT>
<A NAME="Tiger-Open"><B>Why does a font, which worked fine under 10.3 fail
on Mac 10.4 (Tiger)?</B></A>
<DD>
With Tiger (Mac OS/X.4) Apple added some support for OpenType. Some OpenType
features are converted (at runtime) into AAT features. This is good, but
not all features have corresponding Apple feature/settings, and not all lookups
can be converted (conditional lookups cannot be). Unfortunately if a font
contains both OpenType and AAT features Apple now ignores the AAT features
(or so I have been told). The result is that AAT features, which presumably
work, will not be used, while OpenType features, which are not completely
supported and so won't work, are used instead.
<DT>
<A NAME="save-no-change"><B>After I generate a font and quit, why does FontForge
ask if I want to save the font? I didn't change anything.</B></A>
<DD>
There are two reasons why this might be happening.
<OL>
<LI>
Even though you haven't changed anything in this session, FontForge may need
to (re)generate hinting information on one or several glyphs (if, for example
those glyphs have been changed (in an earlier session) but no hints have
been generated for them since). These new hints will mark the font as changed.
<LI>
If your font has an XUID field in the Font Info, then FontForge will increment
the final number in the XUID each time a postscript font is generated --
and this also counts as a change. (Why does FontForge do this? Because Adobe
says it should. A minor annoyance, but it avoids some problems with font
caching when you change an old version of the font for a new one).
</OL>
<DT>
<B><A NAME="TeX">Why doesn't TeX work with my fonts?</A></B>
<DD>
I'm a total novice with TeX. I am told that TeX (or some part of the TeX
chain, dvips perhaps) expects fonts to be encoded in TeX base Encoding --
sometimes called "Adobe Standard" by the TeX docs, but it isn't it's TeX
base. So if you are having printing problems, missing glyphs, etc. try changing
the encoding of your font to TeX Base (Go to Element->Font Info, select
the Encoding tab, select TeX Base from the pulldown list).
<DT>
<A NAME="mf-files"><B>Why doesn't FontForge let me edit an '.mf'
file?</B></A>
<DD>
As Knuth said "(the problem with WSYWYG is that...) What you see is
<I>all</I> you get." FontForge suffers from this.
<P>
Let us take a simple example. Suppose we have a point defined by<BR>
<CODE> top<SUB>1</SUB>y<SUB>2</SUB> = CapHeight</CODE><BR>
And the user tries to drag point 2 to a new y location. How should FontForge
interpret this? It could:
<UL>
<LI>
Change <CODE>CapHeight</CODE>
<LI>
Change the width of pen 1
<LI>
Change the equation to something like:<BR>
<CODE> top<SUB>1</SUB>y<SUB>2</SUB> = CapHeight - 30</CODE>
<LI>
Or to something like:<BR>
<CODE> top<SUB>1</SUB>y<SUB>2</SUB> = (CapHeight +
XHeight)/2</CODE>
<LI>
Or to half a dozen other things.
</UL>
<P>
So FontForge's method for moving a point around is ambiguous. And I haven't
been able to come up with any reasonable way for disambiguating it. Suggestions
are welcome (but there's no guarantee they'll be implemented).
<DT>
<A NAME="minify-iconify"><B>Why does my window get iconified when I want
to minify the view?</B></A>
<DD>
Some window managers (gnome-sawtooth for one) steal meta (alt) clicks from
FontForge. So you can't use meta-middle-click to minify a glyph, you have
to use the View menu->Zoom Out instead.
<DT>
<A NAME="no-mu"><B>Why isn't there a character named "mu" in my greek
font?</B></A>
<DD>
Adobe was thinking more of backwards compatibility than sense when they assigned
the names of the greek letters in their unicode encoding. Thus the name "mu"
refers to the Micro Sign (U+00B5) and not to the letter mu. They also assigned
Delta to Increment, and Omega to Ohm Sign.
<P>
<P>
Adobe has also decided that the character at U+03D6 (said by the Unicode
consortium to refer to "GREEK PI SYMBOL") should be named "omega1", when
"pi1" seems more appropriate.
<DT>
<A NAME="no-copy-names"><B>Why doesn't Edit->Copy copy glyph names as
well as glyph info?</B></A>
<DD>
Firstly because I believe that any attempt to copy a glyph's name will almost
certainly be better done by defining a custom
<A TARGET="_top" HREF="encodingmenu.html">encoding</A>.<BR>
Secondly because most of the time you don't want the name copied.<BR>
Thirdly because it is esthetically better that copy should only work with
data and not meta-data.<BR>
HOWEVER... enough people have asked this question that I've enabled a mode
in <A TARGET="_top" HREF="editmenu.html#CharName">Edit->Copy From->Char
Name</A> which allows you to change the default behavior.
<DT>
<A NAME="copy-names"><B>Why does Edit->Paste complain about name
duplication?</B></A>
<DD>
Because you have Edit->Copy From->Copy Metadata checked. Uncheck it.
<DT>
<A NAME="cidmaps"><B>What on earth are cidmap files and should I care about
them?</B></A>
<DD>
Some background:
<P>
When postscript was invented every glyph in a font was given a name, and
an encoding which was specified by a 256 element array mapping character
codes to names.
<P>
Then they started thinking about CJK fonts (and perhaps Unicode), which have
huge glyph sets, and coming up with reasonable ASCII names for 10,000 glyphs
was <SMALL>a)</SMALL> a waste of space, <SMALL>b)</SMALL> fairly meaningless.
So then adobe created CID-keyed fonts which have no glyph names and no encodings.
Every glyph has an index (a CID), which is just a number, and this is sort
of treated as a name. Then external to the font is an additional resource
(a cmap) which provides the encoding for the font (and can support really
grungy encoding schemes like SJIS), by mapping a sequence of input bytes
to a CID.
<P>
Adobe provides certain standard cmap resources (ie. one for SJIS, one for
JIS, one for Extended Unix whatever). Because these files are fairly painful
to write Adobe has assigned standard meanings to CIDs so that everyone can
use the same cmap file. -- Well actually there are 5 or 6 different standards,
Japanese (JIS208), Japanese (JIS212), Korean, Chinese (Hong Kong, Taiwan),
Chinese (Mainland, Singapore), Identity (Unicode) -- So CID 1 might be space,
CID 2 might be "!", CID 935 might be "Katakana ka", etc.
<P>
My cidmap files just give me a mapping between Adobe's CIDs and Unicode.
This allows FontForge to know what glyph it is working on. If they aren't
present things should work ok, but FontForge would fill the font view with
"?" rather than the appropriate glyph. And FontForge wouldn't be able to
reencode the font into Unicode or anything else.
<P>
<P>
So the cidmap files are only useful for people working on CID keyed CJK fonts.
So many europeans/americans won't need them.
<DT>
<B>Does the <A NAME="simplify">simplify</A> command lose accuracy?</B>
<DD>
Yes it does.<BR>
But not much.<BR>
It is designed to replace a set of splines with another spline that nowhere
differs from the original by more than one unit in the local coordinate
system.<BR>
If this level of accuracy is not good enough then (In the outline view):
<UL>
<LI>
Edit->Select->Select All
<LI>
Element->Transform->Transform
<LI>
Scale Uniformly: 1000%
<LI>
OK
<LI>
Simplify
<LI>
Element->Transform->Transform
<LI>
Scale Uniformly: 10%
<LI>
OK
</UL>
<P>
This will replace a set of splines with a spline that differs from the original
by no more than .1 unit.
<DT>
<A NAME="cubic-quadratic"><B>How does FontForge convert a cubic spline into
a quadratic spline for truetype?</B></A>
<DD>
Again this can involve a loss of accuracy.<BR>
First FontForge checks to see if the spline happens to be a quadratic already
(this would happen if you'd just read in a truetype font, or if a miracle
occurred when you generated the spline).<BR>
Otherwise FontForge will divide the original spline into smaller chunks and
try to find a set of quadratic splines that differ from the cubic by no more
than one unit anywhere. (Once you have picked two end-points and know the
slope at those end-points there is only one quadratic spline possible between
the two).
<DT>
<A NAME="quadratic-cubic"><B>How does FontForge convert a quadratic spline
into a cubic (when reading truetype)?</B></A>
<DD>
This is easy since any quadratic spline can already be represented as a cubic,
it will just happen that the cubic term is always 0.
<P>
Probably the control points will no longer be at integral coordinates and
there will be some loss of precision when they are saved in a cubic format.
<DT>
<B><A NAME="dynamic-libs">Why does fontforge say "Error loading dynamic library"
when trying to import an image file?</A></B>
<DD>
FontForge depends on certain dynamic libraries to load images. It does not
check for the existance of these libraries until you actually try to load
an image. If the library has not been installed on your system it will give
the above error (and fail to load the image).<BR>
The <A HREF="source-build.html#Dependencies" TARGET="_top">Dependencies</A>
section of the main page describes how to find these libraries.<BR>
If the libraries are installed and you still get this message try setting
your LD_LIBRARY_PATH variable to the directory containing the library in
question (On the mac this is DYLD_LIBRARY_PATH).
<DT>
<B><A NAME="complex-eps">Why does fontforge say "EPS file is too complex
to be understood"?</A></B>
<DD>
(Well because it is a misquotation of Shakespeare, and how could I pass that
up? <I>Much Ado About Nothing, V . i. 217</I>)<BR>
Most programs which load eps files treat them as black boxes. They will read
the file into memory and output it, unchanged, to a postscript printer.
Unfortunately FontForge cannot do this. FontForge needs to understand and
then convert the eps file into a simpler format (fonts can use far fewer
operations than an eps file). So unlike most programs FontForge must interpret
each eps file -- but interpretting all of PostScript is a huge job and ff
is limited in what it understands. Sometimes it will find a file it can't
handle.
<DT>
<B><A NAME="Inkscape">Importing glyphs from Inkscape</A></B>
<DD>
(Taken from the <A HREF="http://ospublish.constantvzw.org/?p=340">OSPublish
blog</A> and rewritten by Dave Crossland)
<P>
How to design a glyph in Inkscape so it can readily be imported into fontforge.
<UL>
<LI>
Open Inkscape
<LI>
From the File menu, select Document Properties.
<LI>
Set units to pixels (px) and document dimensions to 1000 x 1000, click OK<BR>
<SMALL>Or if your font has a different number of units per em use that, but
1000 is fontforge's default)</SMALL>
<LI>
Set a horizontal guide at 200px
<LI>
Draw a glyph - the hardest part! :-)
<LI>
Save the drawing as an SVG file
<LI>
Open FontForge
<LI>
From the File menu, select Import, chose SVG, find your drawing, click OK
<LI>
From the Element menu select Transform, set the Y value to -200, click OK
</UL>
<DT>
<A NAME="default-char"><B>How do I set the default glyph of a font?</B></A>
<DD>
If the glyph named ".notdef" contains some splines (but no references) then
it will be used as the default glyph (that is the glyph used when an unencoded
glyph is called for).
<P>
Except that in a OpenType font (that is, a PostScript OpenType font), the
.notdef glyph is not used for the default glyph, instead the "space" glyph
is. (Don't look at me, I didn't write the spec.)
<DT>
<A NAME="ttf-degrade"><B>I loaded a ttf font, made a few changes and generated
a new font. The changed glyphs don't look anywhere near as nice as the originals.
Why?</B></A>
<DD>
When FontForge reads in a truetype font it saves all the hinting (instructions)
that were present in the original. But if you change a glyph in any significant
way those instructions are no longer valid (they depend intimately on the
details of the outlines), so FontForge removes them when you make a change.
The result is that changing a glyph with FontForge will degrade its appearance
in most truetype fonts (not all, some have no hints).<BR>
FontForge can generate truetype instructions for you itself, but you must
ask it to do so -- use the Hints->AutoInstr command.
<DT>
<A NAME="otf-diffs"><B>I generated an opentype font and windows wouldn't
install it. Why not?</B></A>
<DD>
Unfortunately Apple and MicroSoft (and Adobe) do not agree on the proper
format for open and truetype fonts. FontForge has a check box on the Generate
Font Options dialog labelled [] Apple. Make sure this is checked when you
are generating a font for the mac. Make sure this is not checked when generating
a font for Windows (and probably for unix too, though unix tends to be less
picky).
<P>
The major differences I've stumbled onto so far are:
<UL>
<LI>
The postscript name entry in the NAME table.<BR>
(I am told that this is actually an error in Apple's version of the spec,
and the behavior of the Mac matches that of Windows).
<LI>
The names of the tables containing bitmap fonts
<LI>
The way scaled references are stored
<LI>
And the tables containing advanced typographical features are completely
different
</UL>
<DT>
<A NAME="DSIG"><B>I have a truetype font with opentype tables, but windows
displays the "TT" (truetype) icon and not the "O" icon. Why?</B></A>
<DD>
As far as I can tell Windows will mark a truetype font with the "O" icon
if that font contains a 'DSIG' (Digital Signature) table. FontForge does
not produce digital signatures (I think they are of negative utility, and
anyway I don't know how to create them).<BR>
However, it is possible to <A HREF="generate.html#Options" TARGET="_top">ask
FontForge to create a 'DSIG' table </A>which contains no signatures. That
seems enough to make windows happy.
<DT>
<A NAME="names"><B>What do all the different font names mean?</B></A>
<DD>
When <CODE>Element->Font Info</CODE>opens it shows a Names pane with several
different fields. Why are there so many and what do they all mean?
<P>
The Names pane contains names used in PostScript fonts. There is also a
<CODE>TTF Names</CODE> pane which contains a similar set of names used in
sfnts (an sfnt is a font file format which includes truetype, opentype, and
a number of more obscure font formats).
<P>
A font may be PostScript wrapped in an sfnt. In this case it can have both
a set of PostScript names, and a set of sfnt (ttf) names. Those names could
be different (that's usually not a good idea, but they <EM>could</EM> be).
<P>
The "name for humans" is the name traditionally associated with a font. It
might be something like "ITC New Century Schoolbook Italic #4". It's a string
which applications can use to display when they want humans to know what
the font is.
<P>
The fontname exists because PostScript is a programming language and this
is the name used to identify the font <EM>within PostScript</EM>. It has
restrictions on the characters which may be in the name (no spaces is the
biggest. but it also can't look like a number, no parentheses, etc.) and
on the length of the name. It might look like "ITCNewCenturySchoolbook-Italic".
<P>
The family name is the name of a family of related fonts. In the above example
"ITC New Century Schoolbook" would probably be the family name.
<P>
"Base Filename" isn't really a name associated with the font itself. It's
just there to make your life easier when using fontforge. When you generate
a font, ff will pick a default filename for you (you can always change it,
of course, but it is handy if the default name is the one you want to use).
<P>
Normally the default name will be just the fontname with an extension added
(ITCNewCenturySchoolbook-Italic.ttf). But sometimes people want a different
name for the default, perhaps just NewCentSchlBk-Ital.ttf. This lets you
do than.
<P>
So it controls the default FILENAME for the file containing the font, and
does not directly relate to anything in the font itself.
<P>
The weight string is something like "Bold", "Black", "Thin", etc. It does
not include other stylistic variations (you would not put Italic or Condensed
here).
<P>
The copyright string should be self-explanatory.
<HR width="50%">
In addition to the "Names" pane of Font Info, there is also a TTF Names pane.
<P>
In many ways this is a duplicate of the Names pane but with some differences.
It is used to specify names for sfnts.
<P>
Here you have
<UL>
<LI>
Family<BR/>
This corresponds to the PostScript Family
<LI>
SubFamily<BR/>
Vaguely like the weight field, but takes all stylistic varients not just
weight.<BR/>
This might be "Bold", "Italic", "Bold Italic", "SemiBold", "Condensed",
...<BR/>
Whatever is appropriate for your font.
<LI>
Fullname<BR/>
This corresponds to the "Name for humans"
<LI>
Copyright
</UL>
<P>
Generally FontForge will set all these fields appropriately (ie. same as
in the Names pane). If you don't like the name ff chooses you can disassociate
it from the PS name by right clicking on the entry and choosing from the
popup menu.
<HR width="50%">
Further complicating things, there are fields
<UL>
<LI>
WWS Family
<LI>
WWS SubFamily
</UL>
<P>
I don't really understand why these are needed, but MicroSoft thinks they
are. As far as I can tell they should (in most cases) be the same as Family
and SubFamily above, and should therefore be omitted.
<HR width="50%">
CID fontname should be ignored unless you are building a CID keyed font (which
usually means you are working on a CJK font).
<HR width="50%">
Compatible Fullname<BR/>
Is another name I don't see the need for. I think it should be the same as
Fullname, and should be omitted.
<HR width="50%">
TTF Names may be specified in more than one language and writing system.
The entry which is translated most frequently is SubFamily. So for an Italic
font, you would have an English entry "Italic", and perhaps
<UL>
<LI>
French, Italique
<LI>
German, Kursiv
<LI>
Dutch, Cursief
</UL>
<P>
etc.
<DT>
<A NAME="mingliu"><B>I looked at kaiu.ttf or mingliu.ttf and the outlines
looked nothing like the correct glyphs. What's wrong?</B></A>
<DD>
Some truetype fonts (kaiu and mingliu are examples) do not store the correct
outline. Instead they rely on using the instructions to move points around
to generate the outline. The outline does not appear to be grid-fit at all,
just positioned. FontForge will not process the instructions as it reads
the font. In most fonts this would be the wrong thing to do, and I don't
know how I could tell when it needs to be done...
<DT>
<A NAME="greek-accents"><B>When I use Element->Build->Build Accented
Glyph to build one of the Extended Greek glyphs (U+1F00-U+1FFF) FontForge
picks the wrong accents. Why?</B></A>
<DD>
For some reason Unicode has unified greek and latin accents even though they
don't look at all alike. When FontForge follows the simplistic unicode
definitions it will probably pick a latin accent for greek glyphs. Fortunately
Unicode also contains code points for the greek accents starting around U+1FBD,
if you fill these code points with the appropriate accents then FontForge
will use these rather than the latin accents.
<DT>
<A NAME="u-accents"><B>When I use Element->Build->Build Accented Glyph
to build accents over "u" or "y" I get the accent over one of the stems not
centered on the glyph. Why?</B></A>
<DD>
One of your stems is a little taller than the other. FontForge centers accents
over the tallest point on the glyph. If there are several points with the
same height, then an average is used.
<P>
If you make all your stems be the same height then the accent should be properly
centered.
<DT>
<A NAME="ttf2afm"><B>Why does ttf2afm crash on FontForge ttf files?</B></A>
<DD>
I don't know. The ttf2afm that was distributed with my redhat 7.3 linux certainly
did crash. When I downloaded the source from
<A TARGET="_top" HREF="http://www.ctan.org/tex-archive/obsolete/systems/pdftex/">pdftex</A>
area of ctan and built it (with debug) the resultant program did not crash.
Therefore I believe this is a bug in ttf2afm and that bug has been fixed.<BR>
The afm files produced by ttf2afm don't conform to
<A TARGET="_top" HREF="http://partners.adobe.com/asn/developer/PDFS/TN/5004.AFM_Spec.pdf">Adobe's
specifications</A>.
<DT>
<A NAME="memory"><B>My system keeps crashing because FontForge keeps running
out of memory. What can I do about it?</B></A>
<DD>
Buy more memory?
<P>
If you are editing large fonts, FontForge may run out of memory. All too
often when FF runs out of memory, the kernel will crash rather than report
an error condition. FontForge does check for failure to allocate and attempts
to free up some chunks of memory when the system returns an error -- I've
never seen this code activated though.
<P>
FontForge does provide a mechanism which might help you avoid this. FontForge
generally wastes a lot of memory keeping undoes around. You can clear undoes
associated with a glyph with the Edit->Remove Undoes command. You can
also limit the number of undoes that will be stored with each glyph with
the File->Preferences->Editing->UndoDepth.
<DT>
<A NAME="Unstable"><B>Why is FontForge so unstable?</B></A>
<DD>
I don't bother much with doing QA. This is a problem. I don't enjoy doing
it, and no one is paying me to do it, so little gets done.<BR>
If you would like to volunteer to do
<A HREF="mailto:fontforge-devel@lists.sourceforge.net">QA let me know</A>
(this is a public mailing list). It's a thankless job, but important!
<DT>
<B>Why does FontForge look ugly under Xgl/<A NAME="Compiz">Compiz</A>?</B>
<DD>
I haven't the foggiest idea, but I'm told you can fix it by setting:<BR>
<CODE> XLIB_SKIP_ARGB_VISUALS=1</CODE><BR>
for FontForge.
<DT>
<B>Why don't I <A NAME="talk">talk</A> at conferences?</B>
<DD>
Because I have nothing to say.
<TABLE ALIGN=RIGHT>
<TR>
<TD><BLOCKQUOTE ID="lit">
<B><SMALL>TYSON:</SMALL></B><BR>
<TAB INDENT=15>I'm not<BR>
To be found. I'm fully occupied elsewhere.<BR>
If you wish to find me I shall be in my study.<BR>
You can knock, but I shall give you no reply.<BR>
I wish to be alone with my convictions.<BR>
Good night. <I><SMALL>[Exit]</SMALL></I>
<P ALIGN=RIGHT>
<I>The Lady's not for Burning</I><BR>
Christopher Fry
</BLOCKQUOTE>
</TD>
</TR>
</TABLE>
<P>
<BR CLEAR=ALL>
</DL>
<P>
<HR>
<TABLE>
<TR>
<TD>
</TD>
<TD><BLOCKQUOTE ID="lit">
The answer to the Great Question...?<BR>
Yes...!<BR>
Is...<BR>
Yes...!<BR>
Is...<BR>
Yes...!!!...?<BR>
"Forty-two," said Deep Thought with infinite majesty and calm.<BR>
"Forty-two!" yelled Loonquawl, "Is that all you've got to show for seven
and a half million years of work?"<BR>
"I checked it very thoroughly," said the computer, "and that quite definitely
is the answer. I think the problem, to be quite honest with you, is that
you've never actually known what the question is."
<P ALIGN=RIGHT>
<SMALL><I>The Hitchhiker's Guide to the Galaxy</I><BR>
Douglas Adams</SMALL>
</BLOCKQUOTE>
</TD>
</TR>
<TR>
<TD>
</TD>
<TD><BLOCKQUOTE ID="lit">
It's all in Plato, all in Plato: bless me, what do they teach them in these
schools?
<P ALIGN=RIGHT>
<SMALL><I>The Last Battle</I><BR>
C.S. Lewis</SMALL>
</BLOCKQUOTE>
</TD>
</TR>
<TR>
<TD></TD>
<TD><BLOCKQUOTE ID="lit">
"I have answered three questions, and that is enough,"<BR>
Said his father, "Don't give yourself airs!<BR>
Do you think I can listen all day to such stuff?<BR>
Be off, or I'll kick you down stairs."
<P ALIGN=RIGHT>
<SMALL><I>You are old, Father William</I><BR>
Lewis Carroll</SMALL>
</BLOCKQUOTE>
</TD>
</TR>
</TABLE>
<P>
<P ALIGN=Center>
-- <A HREF="sfds/index.html">Prev</A> --
<A HREF="overview.html" TARGET="_top">TOC</A> --
<A HREF="GlossaryFS.html" TARGET="_top">Next</A> --
</DIV>
</BODY></HTML>
|