diff options
Diffstat (limited to 'Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fontname.html')
-rw-r--r-- | Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fontname.html | 46 |
1 files changed, 0 insertions, 46 deletions
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fontname.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fontname.html deleted file mode 100644 index 30a0d7cd095..00000000000 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fontname.html +++ /dev/null @@ -1,46 +0,0 @@ -<head> -<title>UK TeX FAQ -- question label fontname</title> -</head><body> -<h3>What is the “Berry naming scheme”?</h3> -<p/>In the olden days, (La)TeX distributions were limited by the -feebleness of file systems’ ability to represent long names. (The -MSDOS file system was a particular bugbear: fortunately any current -Microsoft system allows rather more freedom to specify file names. -Sadly, the ISO 9660 standard for the structure of CDROMs has a -similar failing, but that too has been modified by various extension -mechanisms.) -<p/>One area in which this was a particular problem was that of file names -for Type 1 fonts. These fonts are distributed by their vendors with -pretty meaningless short names, and there’s a natural ambition to -change the name to something that identifies the font somewhat -precisely. Unfortunately, names such as “BaskervilleMT” are -already far beyond the abilities of the typical feeble file system, -and add the specifier of a font shape or variant, and the difficulties -spiral out of control. Font companies deal with the issue by -inventing silly names, and providing a map file to show what the -“real” names. Thus the Monotype Corporation provides the -translations: -<blockquote> - <code>bas_____ BaskervilleMT</code><br> - <code>basb____ BaskervilleMT-Bold</code><br> - <code>basbi___ BaskervilleMT-BoldItalic</code> -</blockquote><p> -and so on. These names could be used within (La)TeX programs, -except that they are not unique: there’s nothing to stop Adobe using -‘<code>bas_____</code>’ for <em>their</em> Baskerville font. -<p/>Thus arose the Berry naming scheme. -<p/>The basis of the scheme is to encode the meanings of the various parts -of the file’s specification in an extremely terse way, so that enough -font names can be expressed even in impoverished file name-spaces. The -encoding allocates one character to the font “foundry” (Adobe, Monotype, -and so on), two to the typeface name (Baskerville, Times Roman, and so -on), one to the weight, shape, and encoding and so on. -<p/>The whole scheme is outlined in the <i>fontname</i> distribution, -which includes extensive documentation and a set of tables of fonts -whose names have been systematised. -<dl> -<dt><tt><i>fontname distribution</i></tt><dd><a href="http://mirror.ctan.org/info/fontname.zip">info/fontname</a> (or <a href="http://mirror.ctan.org/info/fontname/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/fontname.html">catalogue entry</a> -</dl> -<p/> -<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fontname">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fontname</a> -</body> |