Différences

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

Lien vers cette vue comparative

Les deux révisions précédentes Révision précédente
5_fichiers:fontes:preparer_une_fonte_t1 [2018/12/04 01:16]
jejust
5_fichiers:fontes:preparer_une_fonte_t1 [2021/06/06 19:18] (Version actuelle)
jejust Remise en forme de la page.
Ligne 1: Ligne 1:
-====== Preparing a Type 1 font ======+====== Preparing a Type 1 font ======
  
  
-The process of installing a Type 1 font set is rather convoluted, and+The process of installing a Type(nbsp)1 font set is rather convoluted, and
 we will deal with it in two chunks: first (in the present answer) we will deal with it in two chunks: first (in the present answer)
 preparing the font for installation,​ and second ​ preparing the font for installation,​ and second ​
-[[FAQ-instt1font|installing a Type 1 font]]).+[[5_fichiers:​fontes:​installer_une_police_t1|installing a Type 1 font]]).
  
 Many fonts are supplied in (La)TeX ready form: such fonts need no Many fonts are supplied in (La)TeX ready form: such fonts need no
Ligne 13: Ligne 13:
 via one of the web stores), you are likely to need to "​prepare"​ it for via one of the web stores), you are likely to need to "​prepare"​ it for
 use with (La)TeX. ​ The rest of this answer discusses this preparation. use with (La)TeX. ​ The rest of this answer discusses this preparation.
-  ​ 
  
--  ​Acquire the font.  A very small set of Type 1 fonts is installed +  * **Acquire the font.**  A very small set of Type 1 fonts is installed in most PostScript printers you will encounter. ​ For those few (whose use is covered by the basic PSNFSS package), you don't need the Type 1 font itself, to be able to print using the font.
-    ​in most PostScript printers you will encounter. ​ For those few (whose use +
-    ​is covered by the basic PSNFSS package), you don't need the +
-    ​Type 1 font itself, to be able to print using the font. +
-  ​+
  
-    ​For all the myriad other Type 1 fonts, to be able to print using +For all the myriad other Type 1 fonts, to be able to print using 
-    the font you need the Type 1 file itself. ​ Some of these are +the font you need the Type 1 file itself. ​ Some of these are 
-    available for free (they'​ve either been donated to the public +available for free (they'​ve either been donated to the public 
-    domain, or were developed as part of a free software project), but +domain, or were developed as part of a free software project), but 
-    the vast majority are commercial products, requiring you to spend +the vast majority are commercial products, requiring you to spend 
-    real money. +real money. 
- ​Acquire the fonts' AFM files. ​ AFM files contain + 
-    ​information from the font foundry, about the sizes of the characters +  * **Acquire the fonts' AFM files.**  AFM files contain information from the font foundry, about the sizes of the characters in the font, and how they fit together. ​ One measure of the quality of a font-supplier is that they provide the AFM files by default: if the files are not available, you are unlikely to be able to use the font with (La)TeX. 
-    ​in the font, and how they fit together. ​ One measure of the quality + 
-    ​of a font-supplier is that they provide the AFM files by +  * **Rename the AFM files and the Type 1 files** to match the [[5_fichiers:​fontes:​les_noms_de_fichiers_des_fontes|Berry font naming scheme]]. 
-    ​default: if the files are not available, you are unlikely to be able + 
-    ​to use the font with (La)TeX. +  * **Generate TeX metric files** from the AFM files. ​ The commonest tool for this task is [[ctanpkg>​fontinst]];​ the package documentation helps, but other guides are available (see below). The simplest possible script to pass to [[ctanpkg>​fontinst]] is: 
- ​Rename the AFM files and the Type 1 files to match the +<​code ​latex>
-    ​[[FAQ-fontname|Berry font naming scheme]]. +
- ​Generate TeX metric files from the AFM files. ​ The +
-    ​commonest tool for this task is [[ctanpkg>​fontinst|fontinst]]; the package +
-    ​documentation helps, but other guides are available (see below). +
-    ​The simplest possible script to pass to [[ctanpkg>​fontinst|fontinst]] is: +
-    ```latex+
     \latinfamily{xyz}{}     \latinfamily{xyz}{}
     \bye     \bye
-    ``` +</code>
-    where ''​xyz''​ is the Berry name of the font family. ​ This +
-    simple script is adequate for most purposes: its output covers the +
-    font family in both T1 and OT1 font encodings. ​ Nevertheless,​ +
-    with fancier fonts, more elaborate things are possible with +
-    [[ctanpkg>fontinst|fontinst]]:​ see its documentation for details. +
-  ​+
  
-    ​[[ctanpkg>​Fontinst|Fontinst]] also generates map files, and LaTeX font +where ''​xyz''​ is the Berry name of the font family. ​ This 
-    definition (''​fd''​) files.+simple script is adequate for most purposes: its output covers the 
 +font family in both T1 and OT1 font encodings. ​ Nevertheless,​ 
 +with fancier fonts, more elaborate things are possible with [[ctanpkg>​fontinst]]:​ 
 +see its documentation for details. 
 + 
 + 
 +[[ctanpkg>​fontinst|Fontinst]] also generates map files, and LaTeX font 
 +definition (''​fd''​) files.
  
 Having traversed this list, you have a set of font files ready for Having traversed this list, you have a set of font files ready for
Ligne 58: Ligne 48:
  
 ----- -----
 +//Source:// [[faquk>​FAQ-prept1font|Preparing a Type 1 font]]
  
-//Source:// [[faquk>​FAQ-prept1font|Preparing a Type&​nbsp;​1 font]] +{{htmlmetatags>​metatag-keywords=(LaTeX,​installation,​fontes,​ polices de caractères,​polices PostScript
- +metatag-og:​title=(Preparing a Type 1 font)
-{{htmlmetatags>​metatag-keywords=(LaTeX,​installing+
-metatag-og:​title=(Preparing a Type&nbsp;1 font)+
 metatag-og:​site_name=(FAQ LaTeX francophone) metatag-og:​site_name=(FAQ LaTeX francophone)
 }} }}
  
5_fichiers/fontes/preparer_une_fonte_t1.txt · Dernière modification: 2021/06/06 19:18 par jejust
CC Attribution-Share Alike 4.0 International
Driven by DokuWiki Recent changes RSS feed Valid CSS Valid XHTML 1.0