emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Stefan Nobis <stefan-ml@snobis.de>
To: emacs-orgmode@gnu.org
Subject: Re: fontenc makes pdf non-searchable
Date: Mon, 23 Mar 2015 18:10:55 +0100	[thread overview]
Message-ID: <m17fu7fxls.fsf@nobis-it.eu> (raw)
In-Reply-To: <gjubegofn1dw.fsf@W0144758.usac.mmm.com> (J. David Boyd's message of "Mon, 23 Mar 2015 12:07:23 -0400")

dboyd2@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...,

  reply	other threads:[~2015-03-23 17:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2015-08-05  0:00 ` Bastien Guerry
2015-08-08  2:30   ` Martin Leduc
2015-08-08  8:48     ` Bastien
2015-03-23 22:50 Martin Leduc

Reply instructions:

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 \
    --in-reply-to=m17fu7fxls.fsf@nobis-it.eu \
    --to=stefan-ml@snobis.de \
    --cc=emacs-orgmode@gnu.org \


* 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).