From: Martin Leduc <email@example.com>
To: Stefan Nobis <firstname.lastname@example.org>
Cc: "email@example.com" <firstname.lastname@example.org>
Subject: Re: fontenc makes pdf non-searchable
Date: Mon, 23 Mar 2015 22:50:13 +0000 [thread overview]
Message-ID: <BLU181-W133EB825A64FCB0142A6649A0D0@phx.gbl> (raw)
[-- Attachment #1: Type: text/plain, Size: 1410 bytes --]
You're right, I customized org-latex-pdf-process, which now call a script that basically does latex/dvips/ps2pdf.
I cannot use pdflatex since my figures are from eps images.
dboyd2 <at> mmm.com (J. David Boyd) writes:
> And how did you determine that please?
I assume you mean how I determined that the PDF has been produced by
dvips and Ghostscript. In this case: I've just looked into the
document information of the PDF file. For example with Acrobat Reader
I just press CMD+D, with Apple Preview its CMD+I (look out in the
menus for document information or properties).
In this document information there is somewhere a line like "PDF
creator". If the PDF is created with pdftex or pdflatex, this line
should read something like "pdfTeX-1.40.15".
Each PDF viewer shows a different degree of details about the file.
For example with Apple Preview I do not see the used fonts, these are
only shown by Acrobat Reader (or command line tools like pdffonts from
> And how would it be switched?
The default settings of org-mode uses pdflatex. The compilation
process is configurable via the variable org-latex-pdf-process.
I don't know why and how Martin used dvips+gs. Maybe he just generated
the tex file with org and used another tool for generating PDF. Or
maybe he customized org-latex-pdf-process.
Until the next mail...,
[-- Attachment #2: Type: text/html, Size: 1662 bytes --]
next reply other threads:[~2015-03-23 22:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 22:50 Martin Leduc [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-03-21 4:47 fontenc makes pdf non-searchable Martin Leduc
2015-03-21 16:24 ` William Denton
2015-03-21 18:56 ` Martin Leduc
2015-03-22 17:56 ` William Denton
2015-03-22 23:52 ` Martin Leduc
2015-03-23 7:18 ` Stefan Nobis
2015-03-23 16:07 ` J. David Boyd
2015-03-23 17:10 ` Stefan Nobis
2015-08-05 0:00 ` Bastien Guerry
2015-08-08 2:30 ` Martin Leduc
2015-08-08 8:48 ` Bastien
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).