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