Différences

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

--- fichiers:pdf:produire_des_pdf_cherchables [2018/05/22 11:37] – créée joseph.wright
+++ fichiers:pdf:produire_des_pdf_cherchables [2018/12/04 00:22] (Version actuelle) – jejust
@@ Ligne 1: / Ligne 1: @@
-# Copy-paste-able/searchable PDF files
+====== Copy-paste-able/searchable PDF files ======
@@ Ligne 7: / Ligne 5: @@
 hold their text in the encoding of the original TeX font used by
 the document.
 When PDF readers, etc., offer copy-paste or searching
@@ Ligne 14: / Ligne 11: @@
 documents (in English, at least); the problem comes when you're using
 an inflected language (with accented letters, or composite glyphs
-such as '&aelig;')&nbsp;&mdash; TeX will typically use a non-standard
+such as 'Ã¦') --- TeX will typically use a non-standard
 encoding, and there are likely be problems, since PDF readers
 assume the text is presented in Unicode.
 For PDF generated from LaTeX (the DVI being
-converted, by whatever means), or from PDFLaTeX, the character
+converted, by whatever means), or from pdfLaTeX, the character
 codes used in the PDF file are in fact those of the document's
-[font encoding](./FAQ-whatenc.html); if you're using OT1 or
+[[FAQ-whatenc|font encoding]]; if you're using OT1 or
 T1, your document will be OK for almost all ASCII
-characters, but it's likely that anything ''out of the ordinary'' will
+characters, but it's likely that anything "out of the ordinary" will
 not be represented properly.  (Of course, PDF generated from
 XeTeX- or LuaTeX-based formats is going to be OK, since
-those engines work in Unicode througout.)
+those engines work in Unicode throughout.)
 The solution comes from the character-mapping facilities in the
@@ Ligne 35: / Ligne 30: @@
 version of the characters.
+Packages [[ctanpkg>cmap|cmap]] and [[ctanpkg>mmap|mmap]] both offer means of
-Packages [`cmap`](http://ctan.org/pkg/cmap) and [`mmap`](http://ctan.org/pkg/mmap) both offer means of
+generating such tables ([[ctanpkg>mmap|mmap]] has wider coverage, including
-generating such tables ([`mmap`](http://ctan.org/pkg/mmap) has wider coverage, including
+the various maths encodings); both work with pdfTeX and no other
-the various maths encodings); both work with PDFTeX and no other
 engine.  Thus your document becomes something like:
-```latex
+<code latex>
 \documentclass{article}
 \usepackage{mmap} % (or cmap)
@@ Ligne 47: / Ligne 42: @@
 \begin{document}
 ... % your actual text
-```
+</code>
 Unfortunately, the packages only work with fonts that are directly
-encoded, such as the default (Computer Modern, i.e., `cm`
+encoded, such as the default (Computer Modern, i.e., ''cm''
-fonts, and things such as `cm-super` or the `Latin`
+fonts, and things such as ''cm-super'' or the ''Latin''
-`Modern` sets.  Fonts like Adobe
+''Modern'' sets.  Fonts like Adobe
 Times Roman (which are encoded for (La)TeX use via virtual fonts)
 are not amenable to this treatment.
+-----
+//Source:// [[faquk>FAQ-cpy-srchpdf|Copy-paste-able/searchable PDF files]]
+{{htmlmetatags>metatag-keywords=(LaTeX,usage)
+metatag-og:title=(Copy-paste-able/searchable PDF files)
+metatag-og:site_name=(FAQ LaTeX francophone)
+}}