On Fri, Sep 12, 2008 at 8:13 AM, Yue Wang <[EMAIL PROTECTED]> wrote:
> 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]
\def\onum{\setfontfeature{onum}}
> {\rm\bf\onum\smcp Hello 2008!}
Don't do this, this has nothing to do with logical markup and the
better way is to
write {\definedfont[SerifBold*onum]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?
Hans need fonts to test this but I could provide you a typescript
based solution,
it's not so elegant as the XeTeX method but it works.
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
