>> 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:
>>
>>
Hi Florian,
Florian Wobbe writes:
> 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.
>
>
> 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,
"Li Yanrui (李延瑞)" writes:
> Your example works for me with the beta 2011.01.14 and
> pdftotext-0.16.0.
>
> Which version is your ConTeXt MkIV? Your problem looks like
> "http://www.ntg.nl/pipermail/ntg-context/2010/052259.html"; but that
> one has been solved by Taco.
Hi Li,
ConTeXt ver: 2011.
2011/1/17 Oliver Heins :
> 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
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