ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Yue Wang" <yuleopen@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: One very silly question
Date: Fri, 12 Sep 2008 14:13:25 +0800	[thread overview]
Message-ID: <68bfdc900809112313w2ea5a403s2a6c622af94190bf@mail.gmail.com> (raw)
In-Reply-To: <48C94B39.9080002@wxs.nl>

Hi, Hans:

> no, in such cases, just create another typeface with relevant fonts
> using smallcaps and then switch to that typeface

OK. I see. Thanks.

> hm, it's nbot that complex, just define a featureset and use it; one can
> even adapt features in between if needed (dynamic features)

How to use dynamic features? it is not documented in co-typography and co-fonts.
is there such interface like:

\definefeature[onum][onum=yes]
\definefeature[smcp][smcp=yes]
{\rm\bf\onum\smcp Hello 2008!}

>
> you can be pretty sure that whatever you 'predefine'
> (font-blabla-using-oldstyle-and-smallcaps) will have exceptions and then
> we end up with n! possible combinations

not n!, but 2^n.

last question: is it possible to add fontconfig-like interface? if I
define to use minion famaily, then all the alternatives are
automatically defined like xetex?

Yue Wang
___________________________________________________________________________________
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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2008-09-12  6:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-11 15:21 Yue Wang
2008-09-11 16:45 ` Hans Hagen
2008-09-12  6:13   ` Yue Wang [this message]
2008-09-12  6:29     ` Wolfgang Schuster
2008-09-12  7:11     ` 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=68bfdc900809112313w2ea5a403s2a6c622af94190bf@mail.gmail.com \
    --to=yuleopen@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).