From: Ulrike Fischer <news3@nililand.de>
To: ntg-context@ntg.nl
Subject: Re: copy/paste text broken with certain ligatures
Date: Fri, 15 Apr 2016 13:31:32 +0200 [thread overview]
Message-ID: <1cbzdwt005ew1.dlg@nililand.de> (raw)
In-Reply-To: <5710189A.2000401@wxs.nl>
Am Fri, 15 Apr 2016 00:24:26 +0200 schrieb Hans Hagen:
> On 4/14/2016 3:47 PM, Brian R. Landy wrote:
>> Hi, sometime between version 2015.08.05 and 2016.04.10 the handling of
>> certain ligatures changed (sorry, I don't have intermediate versions to
>> test with). The issue is the ligatures no longer copy/paste as the
>> original two characters, which also breaks text searched of the pdf.
>> Instead they copy as a single glyph.
>>
>> I'm seeing the problem with "ti" and "fj", while others like "ffi",
>> "fi", and "ff" are fine in both versions.
>>
> not all pdf viewers can do that well, unless it's broken, context
> outputs the tounicode vectors needed for it
I can't copy the two ligatures either (in Adobe Reader DC), but with
the equivalent latex example (TL2016 pretest) it works fine. So imho
it is not a viewer problem.
--
Ulrike Fischer
http://www.troubleshooting-tex.de/
___________________________________________________________________________________
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:[~2016-04-15 11:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 13:47 Brian R. Landy
2016-04-14 22:24 ` Hans Hagen
2016-04-15 3:39 ` Brian R. Landy
2016-04-15 11:31 ` Ulrike Fischer [this message]
2016-04-16 13:22 ` Hans Hagen
2016-04-18 14:56 ` Brian R. Landy
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=1cbzdwt005ew1.dlg@nililand.de \
--to=news3@nililand.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).