From: David Wooten <david@farwestmillwork.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: smallcaps with features in simplefont
Date: Wed, 2 Jul 2014 11:29:50 -0700 [thread overview]
Message-ID: <D1D2F2E7-3A9D-4DD9-A18E-AC81226F4CA3@farwestmillwork.com> (raw)
In-Reply-To: <5EBE40B9-2E21-48C9-8053-07A716AB78D7@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1931 bytes --]
Thank you Wolfgang, it’s all coming together.
On Jul 1, 2014, at 9:49 PM, Wolfgang Schuster <schuster.wolfgang@gmail.com> wrote:
>
> Am 01.07.2014 um 23:11 schrieb David Wooten <dw@trichotomic.net>:
>
>> Greetings,
>>
>> I’ve been trying to work through a new font scheme using simplefonts, e.g. in simple form something like this:
>>
>> \definefontfeature[main][protrusion=quality,expansion=quality,onums=yes]
>> \definefontfamily[mainface][rm][Adobe Jenson Pro][features=main]
>> \setupalign[hanging,hz]
>> \setupbodyfont[mainface,13pt]
>>
>> In this setup, I do get protrusion & expansion in the text, —except when I switch to {\sc small caps.}
>
> In your setup you disable ligatures etc., to keep them change the first two lines to
>
> \definefontfeature[main][default][protrusion=quality,expansion=quality,onums=yes]
> \definefontfamily[mainface][rm][Adobe Jenson Pro][features=main]
>
> or
>
> \definefontfeature[main][protrusion=quality,expansion=quality,onums=yes]
> \definefontfamily[mainface][rm][Adobe Jenson Pro][features={default,main}]
>
>> Do I need to declare the caps in some other way?
>
> Smallcaps use the regular where the “smallcaps” features are applied, to use also your “main” features you have to use this setup:
>
> \definefontfamily[mainface][rm][Adobe Jenson Pro][features={default,main},sc=features:{default,main,smallcaps}]
>
> Wolfgang
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
[-- Attachment #1.2: Type: text/html, Size: 3693 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2014-07-02 18:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 21:11 David Wooten
2014-07-02 4:49 ` Wolfgang Schuster
2014-07-02 18:29 ` David Wooten [this message]
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=D1D2F2E7-3A9D-4DD9-A18E-AC81226F4CA3@farwestmillwork.com \
--to=david@farwestmillwork.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).