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 | 12 |
1 files changed, 6 insertions, 6 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 index 2fb347f95f3..a6296c0505a 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fontname.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fontname.html @@ -1,9 +1,9 @@ <head> <title>UK TeX FAQ -- question label fontname</title> </head><body> -<h3>What is the “Berry naming scheme”?</h3> +<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 +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 @@ -11,17 +11,17 @@ 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 +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 +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. <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 +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 letter to the font “foundry”, two to the +encoding allocates one letter to the font “foundry”, two to the typeface name, one to the weight, and so on. 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 |