From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Getting copy-pastable ligatures?
Date: Thu, 04 Dec 2014 16:22:14 +0100 [thread overview]
Message-ID: <54807C26.2030604@wxs.nl> (raw)
In-Reply-To: <0FAF06B9-84CC-465E-8714-CEA77DDCF45E@rna.nl>
On 12/4/2014 3:54 PM, Gerben Wierda wrote:
> On 30 Nov 2014, at 23:38, Hans Hagen <pragma@wxs.nl> wrote:
>
>> On 11/30/2014 1:22 PM, Gerben Wierda wrote:
>>> I’m using mkii. I’d like ot be able to copy-paste words form the
>>> resulting pdf. That works well, except for words that contain ligatures
>>> (e.g. fl fi etc.) Is there a way I can tell (Con)TeXt that the result
>>> must be copy-pastable.
>>>
>>> To make matters slightly more complex I’m using Optima, converted on a Mac:
>>>
>>> \usetypescript[serif,sans,mono] [hanging] [normal]
>>>
>>> % Bypassing type-gtamacfonts.tex
>>> \starttypescript [sans,serif] [optima] [texnansi,ec]
>>> \definefontsynonym [Optima-Regular] [\typescriptthree-OptimaRegular]
>>> [encoding=\typescriptthree]
>>> \definefontsynonym [Optima-Italic] [\typescriptthree-OptimaItalic]
>>> [encoding=\typescriptthree]
>>> \definefontsynonym [Optima-Bold] [\typescriptthree-OptimaBold]
>>> [encoding=\typescriptthree]
>>> \definefontsynonym [Optima-BoldItalic] [\typescriptthree-OptimaBoldItalic]
>>> [encoding=\typescriptthree]
>>> \definefontsynonym [Optima-ExtraBlack] [\typescriptthree-OptimaExtraBlack]
>>> [encoding=\typescriptthree]
>>> \stoptypescript
>>> \starttypescript [sans,serif] [optima] [name]
>>> \setups [font:fallback:\typescriptone]
>>> \definefontsynonym [\typescriptprefix\typescriptone] [Optima-Regular]
>>> \definefontsynonym [\typescriptprefix\typescriptone Italic] [Optima-Italic]
>>> \definefontsynonym [\typescriptprefix\typescriptone Bold][Optima-Bold]
>>> \definefontsynonym [\typescriptprefix\typescriptone BoldItalic]
>>> [Optima-BoldItalic]
>>> \definefontsynonym [\typescriptprefix\typescriptone Black]
>>> [Optima-ExtraBlack]
>>> \stoptypescript
>>> \definetypeface[allsans][rm][serif][optima][default][encoding=texnansi]
>>> \definetypeface[allsans][ss][sans][optima][default][encoding=texnansi]
>>> \loadmapfile [gtamacfonts.map]
>>> \setupbodyfont[allsans,10pt]
>>
>> op zich zou het moeten werken (een tonunicode vector) als er een pdfr-*.mkii file is voor de encoding ... er is er eentje voor ec encoding
>
> Ik ben er niet zo in thuis, maar welke items in bij font setup moet ik dan wijzigen?
texnansi -> ec
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | 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
___________________________________________________________________________________
next prev parent reply other threads:[~2014-12-04 15:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-30 12:22 Gerben Wierda
2014-11-30 22:38 ` Hans Hagen
2014-12-04 14:54 ` Gerben Wierda
2014-12-04 15:22 ` Hans Hagen [this message]
2014-12-05 9:13 ` Gerben Wierda
2015-01-26 16:25 ` Gerben Wierda
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=54807C26.2030604@wxs.nl \
--to=pragma@wxs.nl \
--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).