From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: preventing ligatures in Type1 fonts under MKIV
Date: Wed, 9 Feb 2011 20:22:15 +0100 [thread overview]
Message-ID: <AANLkTi=9f0UQqCc34qRxOojtNvaK8T=kRKmH4bCmy8==@mail.gmail.com> (raw)
In-Reply-To: <5D2DB4FE-882E-444C-99D1-EAD8B009ACCF@gmail.com>
On Wed, Feb 9, 2011 at 19:30, Wolfgang Schuster wrote:
>
> Am 09.02.2011 um 18:03 schrieb Mojca Miklavec:
>
>> Dear Hans,
>>
>> How can I disable fi ligatures and endashes in Lucida Typewriter?
>
> Load the font with texnansi encoding.
How exacly do you mean that; or rather - may I ask for an example? The
current typescript is defined in type-one.mkiv:
\starttypescript [mono] [lucida]
\definefontsynonym [LucidaTypewriter]
[\s!name:LucidaTypewriter]
\definefontsynonym [LucidaTypewriterBold]
[\s!name:LucidaTypewriterBold]
\definefontsynonym [LucidaTypewriterOblique]
[\s!name:LucidaTypewriterOblique]
\definefontsynonym [LucidaTypewriterBoldOblique]
[\s!name:LucidaTypewriterBoldOblique]
\stoptypescript
I could in principle use
\definefontsynonym [LucidaTypewriter] [hlcrt8y] [encoding=texnansi]
but that is probably not what you meant, or at least not something
that would make much sense in the spirit of MKIV "guidelines".
Mojca
___________________________________________________________________________________
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:[~2011-02-09 19:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 17:03 Mojca Miklavec
2011-02-09 18:30 ` Wolfgang Schuster
2011-02-09 19:22 ` Mojca Miklavec [this message]
2011-02-09 19:38 ` Wolfgang Schuster
2011-02-09 22:38 ` Hans Hagen
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='AANLkTi=9f0UQqCc34qRxOojtNvaK8T=kRKmH4bCmy8==@mail.gmail.com' \
--to=mojca.miklavec.lists@gmail.com \
--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).