From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: fontfeatures
Date: Fri, 7 Aug 2009 10:43:55 +0200 [thread overview]
Message-ID: <83ED45A8-EA76-42AA-BB0A-AB98634D7B58@gmail.com> (raw)
In-Reply-To: <4A7B486F.7030505@wxs.nl>
Am 06.08.2009 um 23:17 schrieb Hans Hagen:
> Wolfgang Schuster wrote:
>>
>> what happened with the option to set font features with more
>> memorizable names
>> you mentioned in http://www.ntg.nl/pipermail/ntg-context/2007/028330.html
>> It would be nice to write \definefontfeature[mine][smallcaps=yes]
>> instead
>> of \definefontfeature[mine][smcp=yes] where you have to know the
>> four letter
>> code for the feature.
>
> as mapping is already kin dof present, if you add
>
> for k, v in pairs(to_features) do
> to_features[gsub(k," ","")] = v
> k = lower(k)
> to_features[k] = v
> to_features[gsub(k," ","")] = v
> end
>
> to font-ott.lua then you can say:
>
> \starttext
We should restrict this to one alternative (besides smcp=yes) and
the last variant seems to me like the context way (lowercase keys
without spaces in it).
> % \definefontfeature[smallcaps][smcp=yes,script=latn]
> % \definefontfeature[smallcaps][SmallCapitals=yes,script=latn]
> % \definefontfeature[smallcaps][Small Capitals=yes,script=latn]
> % \definefontfeature[smallcaps][small capitals=yes,script=latn]
> \definefontfeature[smallcaps][smallcapitals=yes,script=latn]
>
> \definedfont[cambria*smallcaps] test
>
> \stoptext
>
> of course you need to memorize the huge feature name table
Why, you can make a table where there normal feature name (Uppercase
with spaces)
is listed together with the normalized form (lowercase, no spaces) and
the four
letter form.
> if needed we can add some extra common entries, like smallcaps and
> oldstyle but someone needs to collect them
Sure, the wiki is a good place for this.
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
___________________________________________________________________________________
next prev parent reply other threads:[~2009-08-07 8:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-05 9:44 fontfeatures Wolfgang Schuster
2009-08-06 21:17 ` fontfeatures Hans Hagen
2009-08-07 8:43 ` Wolfgang Schuster [this message]
2009-08-07 9:10 ` fontfeatures Hans Hagen
2009-08-07 9:28 ` fontfeatures Wolfgang Schuster
2009-08-07 10:05 ` fontfeatures 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=83ED45A8-EA76-42AA-BB0A-AB98634D7B58@gmail.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).