From: Florian Wobbe <Florian.Wobbe@awi.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: searchable PDF with MinionPro under mkiv
Date: Mon, 17 Jan 2011 14:53:01 +0100 [thread overview]
Message-ID: <A0BED3FD-441C-4AFE-B0DF-0E2E9D6FBABB@awi.de> (raw)
In-Reply-To: <87lj2jk69e.fsf@sopos.org>
>> However, it turns out that pdftotext converts to
>>
>> fi ff ffi ffl 1234567890,
>>
>> splitting fi ligature while leaving ff, ffi and ffl intact, which is
>> strange.
>>
>> I did not try with Adobe Reader but the pdf is searchable with Apple
>> Preview and the pasted copy is still intact:
>>
>> fi ff ffi ffl 1234567890
>
> For me, it still doesn't work. I get oldstyle numbers in the text, and
> neither in Adobe Reader nor in okular, evince or xpdf the numbers are
> searchable. However, I figured out that it is my version of the font
> causing the wrong result.
You are right! I have not considered that. Depending on the used font, pdftotext expands (some) the ligatures or not. With TeXGyre Pagella for instance there is no ligature expansion at all:
fi ff ffi ffl 1234567890
and with Cambria I get a pdf which is not searchable with Preview:
i ff fi fl 1234567890
Florian
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2011-01-17 13:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-16 23:30 Oliver Heins
2011-01-17 0:37 ` Li Yanrui (李延瑞)
2011-01-17 1:25 ` Oliver Heins
2011-01-17 11:53 ` Florian Wobbe
2011-01-17 13:29 ` Oliver Heins
2011-01-17 13:53 ` Florian Wobbe [this message]
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A0BED3FD-441C-4AFE-B0DF-0E2E9D6FBABB@awi.de \
--to=florian.wobbe@awi.de \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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.
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 NNTP newsgroup(s).