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 12:53:46 +0100 [thread overview]
Message-ID: <D1B5E901-9517-42F0-BAF1-BC80E1F010F1@awi.de> (raw)
In-Reply-To: <87hbd8l94l.fsf@sopos.org>
> How can I generate a searchable PDF with mkiv, using a non standard font
> like MinionPro?
>
> \definefontfeature [default] [default] [mode=node,script=latn,onum=yes]
> \usemodule[simplefonts]
> \setmainfont[minionpro]
>
> \starttext
> fi ff ffi ffl 1234567890
> \stoptext
>
> Using pdftotext, I get this:
>
> fi ff ffi ffl
Hi Oliver,
it works for me with the beta 2011.01.12 and 2011.01.14 and poppler-0.14.5/ poppler-0.16.0.
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
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
___________________________________________________________________________________
next prev parent reply other threads:[~2011-01-17 11: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 [this message]
2011-01-17 13:29 ` Oliver Heins
2011-01-17 13:53 ` Florian Wobbe
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=D1B5E901-9517-42F0-BAF1-BC80E1F010F1@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).