emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: William Denton <wtd@pobox.com>
To: Martin Leduc <mart_00@hotmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: fontenc makes pdf non-searchable
Date: Sat, 21 Mar 2015 12:24:31 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.02.1503211221490.26756@shell.miskatonic.org> (raw)
In-Reply-To: <BLU181-W46BCBA7BF41683967F88DE9A0F0@phx.gbl>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 838 bytes --]

On 21 March 2015, Martin Leduc wrote:

> I'm using org-mode to write a paper and export it to a pdf. It compiles just fine.
> However, when opening the experted pdf (with evince or okular) and searching for a word, the output from the search function is a list of words with apparently incorrect character encoding.
> I get the same result when compiling directly the exported tex file. However, if I remove the line:
> \usepackage[T1]{fontenc}
> the compiled pdf becomes correctly interpreted by the search function. According to the documentation of the org-article latex class, "There is no facility to disable loading fontenc".

That seems odd to me.  Can you provide an ECM, a minimal complete example, that 
causes this problem?

William Denton ↔  Toronto, Canada ↔  https://www.miskatonic.org/

  reply	other threads:[~2015-03-21 16:24 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 [this message]
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
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=alpine.DEB.2.02.1503211221490.26756@shell.miskatonic.org \
    --to=wtd@pobox.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mart_00@hotmail.com \


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