Martin Leduc writes:
> Hi Bastien, thanks a lot for your response but I finally solved the
> issue by installing the package cm-super.
Thanks for confirming!
--
Bastien
Hi Bastien, thanks a lot for your response but I finally solved the issue by
installing the package cm-super.
Cheers,
Martin
> From: b...@gnu.org
> To: mart...@hotmail.com
> CC: emacs-orgmode@gnu.org
> Subject: Re: fontenc makes pdf non-searchable
> Date: Wed, 5 Aug 2015 02:00:52 +0200
>
> Hi M
Hi Martin,
Martin Leduc writes:
> 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 f
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.
Martin
dboyd2 mmm.com (J. David Boyd) writes:
> And how did you determine that please?
I assume you mean how I determ
dbo...@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 CM
Stefan Nobis writes:
> Martin Leduc 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]{
Martin Leduc 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 gene
works correctly.
Thanks again !
Martin
> Date: Sun, 22 Mar 2015 13:56:45 -0400
> From: w...@pobox.com
> To: mart...@hotmail.com
> CC: emacs-orgmode@gnu.org
> Subject: Re: [O] fontenc makes pdf non-searchable
>
> On 21 March 2015, Martin Leduc wrote:
>
> > You
On 21 March 2015, Martin Leduc wrote:
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}
in the
, and compile it. It should now search normally.
Martin
> Date: Sat, 21 Mar 2015 12:24:31 -0400
> From: w...@pobox.com
> To: mart...@hotmail.com
> CC: emacs-orgmode@gnu.org
> Subject: Re: [O] fontenc makes pdf non-searchable
>
> On 21 March 2015, Martin Leduc wrote:
>
&
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 c
Hi all,
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
12 matches
Mail list logo
