ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: pavneet_arora@waroc.com
Subject: Re: Why does the oldstyle numerals switch, \os, also switch off m-dashes?
Date: Wed, 30 Nov 2011 23:02:04 +0100	[thread overview]
Message-ID: <4ED6A7DC.3070705@wxs.nl> (raw)
In-Reply-To: <3CE3D006-A05F-4627-B53A-DFE9C9057929@googlemail.com>

On 30-11-2011 22:19, Wolfgang Schuster wrote:
>
> Am 30.11.2011 um 20:19 schrieb Pavneet Arora:
>
>> Okay another anomaly:  I used the example in the FAQs to try to set the feature across the entire document, which is really what I want.
>>
>> http://wiki.contextgarden.net/FAQ#How_can_I_get_the_.E2.80.9Coldstyle_numbers.E2.80.9D_.28text_figures.29_in_a_document.3F
>>
>> In a manuscript length project, I wouldn't want to get {\os } for each local instance.  Now, what I have noticed was that the small caps switch, \sc, seems to disable old-style numerals.  Is this a typographic convention, i..e., that in a run of small caps one should not revert to old-style numerals?  Is there a way of avoiding this assumption for a larger project?  I sometimes have text set in small caps that as part of a project ID would have some numbers in it.  In that case, I would like the old-style numerals to be used.
>
> No, the answer is that smallcaps are activated with the “smcp” feature and this is applied to the regular style with the “smallcaps” set. To get now old style figures when you use smallcaps letters you need also this setup:
>
> \definefontfeature[smallcaps][smallcaps][onum=yes]

given that the smallcaps feature does not nil oldstyle (happens in some 
fonts)


-----------------------------------------------------------------
                                           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
___________________________________________________________________________________


  parent reply	other threads:[~2011-11-30 22:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-30  1:19 Pavneet Arora
2011-11-30  6:30 ` Wolfgang Schuster
2011-11-30 12:28   ` Pavneet Arora
2011-11-30 19:19   ` Pavneet Arora
2011-11-30 19:45     ` Willi Egger
2011-11-30 21:19     ` Wolfgang Schuster
2011-11-30 22:01       ` Pavneet Arora
2011-11-30 22:02       ` Hans Hagen [this message]
2011-12-02  0:26       ` Pavneet Arora

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=4ED6A7DC.3070705@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=ntg-context@ntg.nl \
    --cc=pavneet_arora@waroc.com \
    /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).