From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: bug in \definefontfamily?
Date: Sun, 19 Mar 2017 22:22:27 +0100 [thread overview]
Message-ID: <58CEF693.5040909@gmail.com> (raw)
In-Reply-To: <6bb00b67-4c9d-0a85-1779-29f287de3255@gmx.es>
[-- Attachment #1.1: Type: text/plain, Size: 956 bytes --]
> Pablo Rodriguez <mailto:oinos@gmx.es>
> 19. März 2017 um 22:08via Postbox
> <https://www.postbox-inc.com/?utm_source=email&utm_medium=sumlink&utm_campaign=reach>
>
> Yes, this might work, but I’m afraid I need to disable other default
> features such as ligatures (not only liga, but TeX ligatures).
>
> I had this problem typesetting XML sources and I didn’t know how to
> disable the other features.
The default setting is “feature=default” and to get expansion/protrusion
additional
to kerning etc. you have two options:
1. Add them to the default feature with
\definefontfeature[default][default][expansion=quality,protrusion=quality]
2. Set multiple feature with
\definefontfamily[...][...][...][features={default,quality}]
You can use the second method when you want only expansion/protrusion.
When you
set only “features=quality” kerning isn’t enabled because the default
features aren’t
applied to your font.
Wolfgang
[-- Attachment #1.2: Type: text/html, Size: 2127 bytes --]
[-- Attachment #2: Type: text/plain, Size: 492 bytes --]
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2017-03-19 21:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-18 22:05 OT salt feature not working? Pablo Rodriguez
2017-03-19 10:11 ` Pablo Rodriguez
[not found] ` <58ce6920.42ba1c0a.ea8e8.7871@mx.google.com>
2017-03-19 12:38 ` bug in \definefontfamily? (was: Re: OT salt feature not working?) Pablo Rodriguez
2017-03-19 19:38 ` bug in \definefontfamily? Wolfgang Schuster
2017-03-19 20:07 ` Pablo Rodriguez
2017-03-19 20:32 ` Wolfgang Schuster
2017-03-19 20:40 ` Pablo Rodriguez
2017-03-19 20:46 ` Wolfgang Schuster
2017-03-19 20:58 ` Wolfgang Schuster
2017-03-19 21:08 ` Pablo Rodriguez
2017-03-19 21:22 ` Wolfgang Schuster [this message]
2017-03-20 12:59 ` Hans Hagen
2017-03-20 12:55 ` 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=58CEF693.5040909@gmail.com \
--to=schuster.wolfgang@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).