Différences

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

--- fichiers:fontes:installer_une_police_t1 [2018/06/03 13:36] – samcarter
+++ 5_fichiers:fontes:installer_une_police_t1 [2022/07/05 14:48] (Version actuelle) – <> → ⟨⟩ dbitouze
@@ Ligne 1: / Ligne 1: @@
----
+====== Installing a Type 1 font ======
-title: Installing a Type&nbsp;1 font
-category: installing
-permalink: /FAQ-instt1font
-date: 2014-06-10
----
-Once you have a prepared Type&nbsp;1 font, either direct from CTAN
-or the like, or having ["prepared" it yourself](FAQ-prept1font),
+Once you have a prepared Type(nbsp)1 font, either direct from CTAN or the like,
+or having [[5_fichiers:fontes:preparer_une_fonte_t1|"prepared" it yourself]],
 you can get on with installation.
 The procedure is merely an extension of that for packages, etc., so
 much of what follows will be familiar:
--  Install the files, in your local `texmf` tree (the advice
+  * **Install the files**, in your local ''texmf'' tree (the advice about installing non-standard things applies here, too).  The following list gives reasonable destinations for the various files related to a font family ''⟨//fname//⟩'':
-    about installing non-standard things applies here, too).  The
-    following list gives reasonable destinations for the various files
-    related to a font family &lsaquo;_fname_&rsaquo;:
-    ```
-    .pfb,
-    .pfa  .../fonts/type1/<foundry>/<fname>
-    .tfm  .../fonts/tfm/<foundry>/<fname>
-    .vf   .../fonts/vf/<foundry>/<fname>
-    .sty,
-    .fd   .../tex/latex/<fname>
-    .map  .../fonts/map/dvips/<foundry>
-    ```
-    but if you are lucky, you will be starting from a distribution from
-    CTAN and there is a corresponding `tds.zip` file:
-    using this TDS-file saves the bother of deciding where to put
-    your files in the TDS tree.
--  Regenerate the file indexes (as described in
-    [package installation](FAQ-inst-wlcf)).
--  Update the `dvips`, pdfTeX and other maps:
-  -  On any current TeX&nbsp;Live-based system, or a teTeX v3.0
+^  Extension  ^  Path  ^
-      system, execute the command
+| ''.pfb'', ''.pfa''  | ''.../fonts/type1/⟨//foundry//⟩/⟨//fname//⟩''  |
-    ```
+| ''.tfm''            | ''.../fonts/tfm/⟨//foundry//⟩/⟨//fname//⟩''    |
-    updmap-sys --enable Map <fname>.map
+| ''.vf''             | ''.../fonts/vf/⟨//foundry//⟩/⟨//fname//⟩''     |
-    ```
+| ''.sty'', ''.fd''   | ''.../tex/latex/⟨//fname//⟩''                  |
-      as root.  (If you _can_ use `updmap-sys`&nbsp;&mdash; do; if
+| ''.map''            | ''.../fonts/map/dvips/⟨//foundry//⟩''          |
-      not&nbsp;&mdash; presumably because your (La)TeX system was set up by
-      someone else&nbsp;&mdash; you have to fall back on plain `updmap`,
+but if you are lucky, you will be starting from a distribution from
-      but be aware that it's a potent source of confusion, setting up
+CTAN and there is a corresponding ''tds.zip'' file:
-      map sets that might be changed behind your back.)
+using this TDS-file saves the bother of deciding where to put
-  -  On a current MiKTeX system, update the system file
+your files in the TDS tree.
-      `updmap.cfg`, using the shell command
-    ```
+  * **Regenerate the file indexes** (as described in [[5_fichiers:installer_des_fichiers_pour_latex|package installation]]):
-    initexmf --edit-config-file updmap
-    ```
+  * **Update the maps** for ''dvips'', pdfTeX and others:
-      adding a line at the end:
-    ```
+On any current TeX Live-based system, or a teTeX v3.0 system, execute the command
-    Map <fname>.map
+<code bash>
-    ```
+updmap-sys --enable Map ⟨fname⟩.map
-      for each font family &lsaquo;_fname_&rsaquo; you are adding to the system.
+</code>
-      Now generate revised maps with the shell command
+as root.  (If you //can// use ''updmap-sys'' --- do; if
-    ```
+not --- presumably because your (La)TeX system was set up by
+someone else --- you have to fall back on plain ''updmap'',
+but be aware that it's a potent source of confusion, setting up
+map sets that might be changed behind your back.)
+On a current MiKTeX system, update the system file ''updmap.cfg'', using the shell command
+<code bash>
+initexmf --edit-config-file updmap
+</code>
+adding a line at the end:
+<code text>
+Map ⟨fname⟩.map
+</code>
+for each font family ⟨//fname//⟩ you are adding to the system.
+Now generate revised maps with the shell command
+<code bash>
     initexmf --mkmaps
-    ```
+</code>
-      This, and other matters, are described in MiKTeX
-      ["advanced" documentation](http://docs.miktex.org/manual/advanced.html).
+This, and other matters, are described in MiKTeX
+[[http://docs.miktex.org/manual/advanced.html|"advanced" documentation]].
+Both processes (preparing and installing a font) are very well (and thoroughly)
+described in Philipp Lehman's [[ctanpkg>fontinstallationguide|guide to font installation]].
-Both processes (preparing and installing a font) are very well (and
-thoroughly) described in Philipp Lehman's guide to font installation,
-which may be found on CTAN.
+-----
+//Source:// [[faquk>FAQ-instt1font|Installing a Type 1 font]]
+{{htmlmetatags>metatag-keywords=(LaTeX,installation,fontes,polices de caractères,polices PostScript)
+metatag-og:title=(Installing a Type 1 font)
+metatag-og:site_name=(FAQ LaTeX francophone)
+}}