emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: dboyd2@mmm.com (J. David Boyd)
To: emacs-orgmode@gnu.org
Subject: Re: fontenc makes pdf non-searchable
Date: Mon, 23 Mar 2015 12:07:23 -0400	[thread overview]
Message-ID: <gjubegofn1dw.fsf@W0144758.usac.mmm.com> (raw)
In-Reply-To: m1d240gp0f.fsf@nobis-it.eu

Stefan Nobis <stefan-ml@snobis.de> writes:

> Martin Leduc <mart_00@hotmail.com> writes:
>> You can find a minimal example here[1], with the org file, and the
>> tex and pdf files generated from it. Firts try to search within the
>> pdf. It does not work (at least on my side) To solve the problem,
>> remove the line with \usepackage[T1]{fontenc}
> Your PDF is not generated with pdflatex (or a newer engine like
> lualatex), but with dvips and Ghostscript. Thus the fonts are not PS
> Type 1 fonts, but Type 3 fonts (bitmap instead of vector; therefore
> scaling/zooming will result in bad quality).
> I'm not quite sure if this is also the root cause of the inability to
> search. But if i recompile your tex-file (from [1]) with pdflatex, I
> get Type 1 fonts and have no problems with searching.
> Therefore I would suggest to switch the engine to pdflatex.
> Another hint: You should try the Latin Modern font (put a
> "\usepackage{lmodern}" after loading fontenc) -- it's the
> (technically) modern variant of Computer Modern (the old TeX default
> font). Lati Modern is available as OpenType font and has less problems
> with Unicode and special characters like german umlauts (ä, ü,...) or
> other non-ASCII letters.
> And maybe you should also have a look at biblatex[2] (as a much more
> flexible alternative to natbib).
> [1] https://www.dropbox.com/sh/7s6di4en5ljbkcq/AAAzyQeg6VkMHnC1X9dQTg6ua?dl=0
> [2] http://ctan.org/pkg/biblatex

And how did you determine that please?   And how would it be switched?


  reply	other threads:[~2015-03-23 16:07 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 [this message]
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
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=gjubegofn1dw.fsf@W0144758.usac.mmm.com \
    --to=dboyd2@mmm.com \
    --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).