Différences

Ci-dessous, les différences entre deux révisions de la page.

--- fichiers:fontes:les_noms_de_fichiers_des_fontes [2018/05/23 20:26] – joseph.wright
+++ 5_fichiers:fontes:les_noms_de_fichiers_des_fontes [2021/06/06 17:24] (Version actuelle) – Correction des mots-clefs OpenGraph. Remise en forme. jejust
@@ Ligne 1: / Ligne 1: @@
----
+====== What is the “Berry naming scheme”? ======
-ID: Q-fontname
-section: Bits and pieces of (La)TeX
-revised: 2014-06-10
----
-# What is the ''Berry naming scheme''?
 In the olden days, (La)TeX distributions were limited by the
@@ Ligne 10: / Ligne 6: @@
 MS-DOS file system was a particular bugbear: fortunately any current
 Microsoft system allows rather more freedom to specify file names.
-Sadly, the ISO&nbsp;9660 standard for the structure of CD-ROMs has a
+Sadly, the ISO(nbsp)9660 standard for the structure of CD-ROMs has a
 similar failing, but that too has been modified by various extension
 mechanisms.)
 One area in which these short file names posed a particular problem
-was that of file names for Type&nbsp;1 fonts.
+was that of file names for Type(nbsp)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
+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
+"real" names.  Thus the Monotype Corporation provides the translations:
-translations:
-  `bas_____ BaskervilleMT`
-  `basb____ BaskervilleMT-Bold`
+<code>
+  bas_____ BaskervilleMT
-  `basbi___ BaskervilleMT-BoldItalic`
+  basb____ BaskervilleMT-Bold
+  basbi___ BaskervilleMT-BoldItalic
+</code>
 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
-`bas_____` for _their_ Baskerville font.
+''bas____'' for //their// Baskerville font.
 Thus arose the Berry naming scheme.
@@ Ligne 40: / Ligne 36: @@
 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,
+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.
-The whole scheme is outlined in the [`fontname`](https://ctan.org/pkg/fontname) distribution,
+The whole scheme is outlined in the [[ctanpkg>fontname]] distribution,
 which includes extensive documentation and a set of tables of fonts
 whose names have been systematised.
+-----
+//Source:// [[faquk>FAQ-fontname|What is the “Berry naming scheme”?]]
+{{htmlmetatags>metatag-keywords=(LaTeX,concepts,fontes,polices de caractères,noms des fichiers)
+metatag-og:title=(What is the “Berry naming scheme”?)
+metatag-og:site_name=(FAQ LaTeX francophone)
+}}