From: Vit Zyka <vit.zyka@seznam.cz>
Subject: Re: Ligature handling for PDF searching.
Date: Wed, 27 Jul 2005 10:04:17 +0200 [thread overview]
Message-ID: <42E74001.8010501@seznam.cz> (raw)
In-Reply-To: <4.3.1.2.20050726204553.01d32a58@cits1.stanford.edu>
Brooks Moses wrote:
> (This came up on comp.text.tex in a question about LaTeX, but it also
> applies to ConTeXt, and the proposed solution for LaTeX doesn't apply.)
>
> Consider the following document:
>
> \starttext
> Some ligature tests: ff, fi, ffi, fl, ffl.
> \stoptext
>
> If I process that with texexex -pdf, load it into Acrobat 5, and then
> copy-and-paste the text from the PDF into a text editor, the fi and fl
> ligatures are correctly treated as two letters, but the ff, ffi, and ffl
> ligatures are treated as single (unknown) characters. Similarly,
> searching for "f" within the document only finds the fi and fl
> ligatures; it doesn't find the others. Searching for "ff" finds nothing.
>
> This is a fairly significant problem in the on-screen usability of
> ConTeXt-created documents.
>
> In LaTeX, there is apparently a solution in the cmap.sty package (though
> it currently only works for T1 encoding):
> http://www.ctan.org/tex-archive/macros/latex/contrib/cmap/
>
> Is there a similar solution for ConTeXt? (Has this perhaps been solved
> with a later version of ConTeXt than I have on my computer?)
Yes, but IFAIK only for one or two encodings (CMAP files). I have to
remember ... the keyword is \usepdffontresource. See source enco-pfr.tex
for more info.
vit
prev parent reply other threads:[~2005-07-27 8:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-27 3:52 Brooks Moses
2005-07-27 7:37 ` Hans Hagen
2005-07-27 8:25 ` Taco Hoekwater
2005-07-27 8:50 ` Brooks Moses
2005-07-27 9:13 ` Taco Hoekwater
2005-07-27 10:35 ` Hans Hagen
2005-07-27 8:04 ` Vit Zyka [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=42E74001.8010501@seznam.cz \
--to=vit.zyka@seznam.cz \
--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).