ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Small capitals broken in latest beta?
Date: Sun, 3 Apr 2011 18:43:47 +0200	[thread overview]
Message-ID: <FF0AA486-D9CF-4D27-A3F8-8C456A535F92@googlemail.com> (raw)
In-Reply-To: <000f01cbf204$09be0470$1d3a0d50$@gmx.de>


Am 03.04.2011 um 15:35 schrieb C.:

> Wolfgang, your solution works for the small caps, even without defining the font feature. I guess it's because \sc is a standard (la)tex style switch like \it.

No, context doesn’t provide latex style switches but you can define them with

\definealternativestyle [bfseries] [\bf]
\definealternativestyle [itseries] [\it]

> Defining (or at least using) the other font feature (c2sc) does not work, and since (to my knowledge) there is no style like \sc for that in tex,
> we have to define it using the font feature.

In MKII \sc switch to a different font but MKIV can just enable the “smcp” feature.

Adding “smcp=yes” doesn’t work as option for \setmainfont because you can
use \definfontfeature and overload the “default” set, the only valid options
from \definefontfeature are “script”, “expansion” and “protrusion”.

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
___________________________________________________________________________________


  parent reply	other threads:[~2011-04-03 16:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-01 22:40 C.
2011-04-02  6:09 ` Wolfgang Schuster
2011-04-03  7:41   ` Bernhard Rosensteiner
2011-04-03 13:35     ` C.
2011-04-03 16:30       ` Bernhard Rosensteiner
2011-04-03 16:38         ` Wolfgang Schuster
2011-04-03 17:02         ` C.
2011-04-04  8:14           ` Bernhard Rosensteiner
2011-04-03 16:43       ` Wolfgang Schuster [this message]
2011-04-04 10:50         ` C.
2011-04-04 10:56           ` Wolfgang Schuster
2011-04-04 15:38             ` C.
2011-04-04 20:29               ` John Haltiwanger
     [not found]                 ` <003401cbf309$cd8baf50$68a30df0$@gmx.de>
2011-04-04 20:54                   ` John Haltiwanger
2011-04-04 21:02                     ` Wolfgang Schuster

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=FF0AA486-D9CF-4D27-A3F8-8C456A535F92@googlemail.com \
    --to=schuster.wolfgang@googlemail.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).