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édentesRévision précédente
Prochaine révision
Révision précédente
fichiers:fontes:ou_sont_les_fontes_am [2018/06/03 13:33] samcarter5_fichiers:fontes:ou_sont_les_fontes_am [2022/11/30 20:36] (Version actuelle) – Codes nettoyés dbitouze
Ligne 1: Ligne 1:
---- +====== Where are the ''am'' fonts? ======
-title: Where are the `amfonts? +
-category: errors +
-tags: deprecated +
-permalink: /FAQ-amfonts +
-date: 2014-06-10 +
----+
  
-One _still_ occasionally comes across a request for the `am`+ 
 +One //still// occasionally comes across a request for the ''am''
 series of fonts.  The initials stood for "Almost [Computer] Modern", series of fonts.  The initials stood for "Almost [Computer] Modern",
 and they were the predecessors of the Computer Modern fonts that we and they were the predecessors of the Computer Modern fonts that we
-all know and love (or hate) +all know and love (or hate).
-<sup class="fmk">&dagger;</sup><span class="footnote">&dagger;  +
-  The fonts acquired their label "Almost" following the realisation +
-  that their first implementation in MetaFont79 still wasn't quite right; +
-  Knuth's original intention had been that they were the final answer. +
-</span>.+
 There's not a lot one can do with these There's not a lot one can do with these
 fonts; they are (as their name implies) almost (but not quite) the fonts; they are (as their name implies) almost (but not quite) the
-same as the `cmseries; if you're faced with a document that requests+same as the ''cm'' series; if you're faced with a document that requests
 them, the only reasonable approach is to edit the document to replace them, the only reasonable approach is to edit the document to replace
-`am*font names with `cm*`.+''am**'' font names with ''cm**''
 + 
 +//† The fonts acquired their label "Almost" following the realisation that their first implementation in MetaFont79 still wasn't quite right; Knuth's original intention had been that they were the final answer. 
 +//
  
 The appearance of DVI files that request them is sufficiently The appearance of DVI files that request them is sufficiently
Ligne 26: Ligne 19:
 translation of them by means of virtual fonts. translation of them by means of virtual fonts.
  
-You therefore have to fool the system into using `cm*fonts +You therefore have to fool the system into using ''cm*'' fonts 
-where the original author specified `am*`.+where the original author specified ''am*''.
  
 One option is the font substitutions that many One option is the font substitutions that many
-DVI drivers provide via their configuration file&nbsp;&mdash; +DVI drivers provide via their configuration file --- 
-specify that every `amfont should be replaced by its +specify that every ''am'' font should be replaced by its 
-corresponding `cmfont.+corresponding ''cm'' font.
  
-Alternatively, one may try DVI editing&nbsp;&mdash; packages +Alternatively, one may try DVI editing --- packages 
-[`dtl`](https://ctan.org/pkg/dtl) (DVI Text Language) and [`dviasm`](https://ctan.org/pkg/dviasm)+[[ctanpkg>dtl|dtl]] (DVI Text Language) and [[ctanpkg>dviasm|dviasm]]
 (DVI assembler) can both provide round trips from DVI to (DVI assembler) can both provide round trips from DVI to
 text and back to DVI.  One therefore edits font names text and back to DVI.  One therefore edits font names
Ligne 43: Ligne 36:
 The DTL text is pretty straightforward, for this purpose: The DTL text is pretty straightforward, for this purpose:
 fontnames are in single quotes at the end of lines, so: fontnames are in single quotes at the end of lines, so:
-  `dv2dt -o` &lsaquo;_doc.txt_&rsaquo; &lsaquo;_doc.dvi_&rsaquo;+  dv2dt -o ⟨doc.txt⟩ ⟨doc.dvi⟩
  
-  (_edit the `txt` file_)+//edit the ''txt'' file//
  
-  `dt2dv -o` &lsaquo;_edited.dvi_&rsaquo; &lsaquo;_edited.txt_&rsaquo;+  dt2dv -o ⟨edited.dvi⟩ ⟨edited.txt⟩
 (you have to compile the C programs for this). (you have to compile the C programs for this).
  
-`Dviasmis a `Pythonscript; its output has font+''Dviasm'' is a ''Python'' script; its output has font
 names in a section near the start of the document, and then dotted names in a section near the start of the document, and then dotted
 about through the body, so: about through the body, so:
-  `python dviasm.py -o` &lsaquo;_doc.txt_&rsaquo; &lsaquo;_doc.dvi_&rsaquo;+  python dviasm.py -o ⟨doc.txt⟩ ⟨doc.dvi⟩
  
-  (_edit the `txt` file_)+//edit the ''txt'' file//
  
-  `python dviasm.py -o` &lsaquo;_edited.dvi_&rsaquo; &lsaquo;_edited.txt_&rsaquo;+  python dviasm.py -o ⟨edited.dvi⟩ ⟨edited.txt⟩
 Both routes seem acceptable ways forward; it is a matter of taste Both routes seem acceptable ways forward; it is a matter of taste
 which any particular user may choose (it's not likely that it will be which any particular user may choose (it's not likely that it will be
 necessary very often...). necessary very often...).
  
 +
 +-----
 +
 +//Source:// [[faquk>FAQ-amfonts|Where are the am fonts?]]
 +
 +{{htmlmetatags>metatag-keywords=(LaTeX, messages d'erreurs, format DVI, polices, Metafont)
 +metatag-og:title=(Where are the am fonts?)
 +metatag-og:site_name=(FAQ LaTeX francophone)
 +}}
  
5_fichiers/fontes/ou_sont_les_fontes_am.1528032787.txt.gz · Dernière modification : 2018/06/03 13:33 de samcarter
CC Attribution-Share Alike 4.0 International
Driven by DokuWiki Recent changes RSS feed Valid CSS Valid XHTML 1.0