From: Willi Egger <w.egger@boede.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Fontfeature: smcp
Date: Fri, 7 Jan 2011 12:23:06 +0100 [thread overview]
Message-ID: <C0C36595-DFDE-47AC-AC63-AF8F06403FFC@boede.nl> (raw)
In-Reply-To: <455DA504-8DB0-4658-9478-43DC1E51561B@gmail.com>
Hi Wolfgang,
thanks for your help!. Still no avail...
My script looks now like
\definefontfeature[smcp][default][smcp=yes]
\starttypescript [sans] [seravek] [name]
\definefontsynonym [Seravek-Roman] [file:Seravek-Regular] [features=default]
\stoptypescript
\starttypescript [sans] [seravek]
\definefontsynonym [Sans] [Seravek-Roman] [features=default]
\definefontsynonym [SansCaps] [Seravek-Roman] [features=smcp]
\stoptypescript
\starttypescript [Seravek]
\definetypeface [Seravek] [ss] [sans][seravek][default]
\definetypeface [Seravek] [mm] [math][palatino][default]
\stoptypescript
%\def\sc{\addff{smcp}}
\starttext
{\sc Smallcaps: \fontname\font. Amsterdam, 1234567890}
\stoptext
This gives no smallcaps wether the \def is active or not.
Strange thing is, that is works with lm and pagella (tested).
Willi
On 7 Jan 2011, at 11:22, Wolfgang Schuster wrote:
>
> Am 06.01.2011 um 23:02 schrieb Willi Egger:
>
>> Hm, has something change in the way a font feature should be implemented?
>>
>> \definefontsynonym [SansRegularCaps] [Sans] [ features=smallcaps]
>
> \definefontsynonym [SansCaps] [Sans] [features=smallcaps]
>
>>
>> If I add \def\sc{\addff{smcp} I get still no smallcaps.
>
> You need \definefonfeature[smcp][smcp=yes] to enable a feature with \addff or \addfs.
>
> 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
> ___________________________________________________________________________________
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2011-01-07 11:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 22:02 Willi Egger
2011-01-07 10:22 ` Wolfgang Schuster
2011-01-07 11:23 ` Willi Egger [this message]
2011-01-07 11:33 ` Wolfgang Schuster
2011-01-07 13:18 ` Willi Egger
2011-01-07 13:23 ` Willi Egger
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=C0C36595-DFDE-47AC-AC63-AF8F06403FFC@boede.nl \
--to=w.egger@boede.nl \
--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).