ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Brian R. Landy" <brian@landy.cx>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: copy/paste text broken with certain ligatures
Date: Thu, 14 Apr 2016 23:39:40 -0400	[thread overview]
Message-ID: <FA998102-EAE9-42CA-A1DA-0751770A033E@landy.cx> (raw)
In-Reply-To: <5710189A.2000401@wxs.nl>


> On Apr 14, 2016, at 6:24 PM, Hans Hagen <pragma@wxs.nl> wrote:
> 
>> 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.
>> 
>> I see this using Calibri (other fonts I tried don't support those two
>> ligatures):
>> 
>>   \starttypescript[cleartype]
>>     \definetypeface[\typescriptone][ss][sans][calibri][default]
>>   \stoptypescript
>>   \usetypescript[cleartype]
>>   \setupbodyfont[cleartype,sans,10pt]
>>   \starttext
>>   ffi\par
>>   fi\par
>>   ff\par
>>   fi\par
>>   ti\par
>>   fj\par
>>   \stoptext
>> 
>> Thank you.
> 
> not all pdf viewers can do that well, unless it's broken, context outputs the tounicode vectors needed for it
> 
> Hans

But Acrobat works fine with the pdf generated by the older version of ConTeXt, which also uses the ligatures. So something must be different about the files generated by the two versions?

I can post examples tomorrow if you'd like. 

Thanks,
Brian

> 
> -----------------------------------------------------------------
>                                          Hans Hagen | PRAGMA ADE
>              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>      tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl
> -----------------------------------------------------------------
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2016-04-15  3:39 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 [this message]
2016-04-15 11:31   ` Ulrike Fischer
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=FA998102-EAE9-42CA-A1DA-0751770A033E@landy.cx \
    --to=brian@landy.cx \
    --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).