Hans Hagen wrote:
> Taco Hoekwater wrote:
>
>> But that doesnt help unless it happens automaticallly. Somewhere down
>> in the typescript there is a:
>>
>> \definefontsynonym [SansCaps] [Sans] [features=smallcaps]
>>
>> and currently to have expansion added to that font you have to redefine
>> the font synonyms one way or another, either via
>>
>> \definefontfeature[hz-smallcaps][smallcaps][expansion=quality]
>> ...
>> \definefontsynonym [SansCaps] [Sans] [features=hz-smallcaps]
>>
>> or via
>>
>> \definefontfeature[plushz][expansion=quality]
>> ...
>> \definefontsynonym [SansCaps] [Sans] [features={smallcaps,plushz}]
>>
>> but in both cases quite a lot of lines have to be redone.
>>
>>
>> If MKIV would allow
>>
>> \definetypeface [][][][][][extrafeatures=plushz]
>>
>> so that the font synonym would then automatically be interpreted as
>>
>> \definefontsynonym [SansCaps] [Sans] [features={smallcaps,plushz}]
>>
>> that would be useful (i think so, at least)
>
> sure, but then we need an extraextraextrafeatures later, so i'd rather
how so? simply adding feature names to the end of the list is an
extensible solution, i thought.
> ponder about an extendable solution; kind of
> \definefontfeature[extras][]
>
> \definefontfeature[plushz][expansion=quality]
>
> \definefontfeature[extras][plushz]
anyway, this also sounds good.
> \definefontsynonym [SansCaps] [Sans] [features={smallcaps,extras}]
>
> anyhow, the whole feature support is somewhat floating and will be
> extended anyway
>
>
>
> Hans
>
> -----------------------------------------------------------------
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
> | www.pragma-pod.nl
> -----------------------------------------------------------------
_______________________________________________
dev-context mailing list
[email protected]
http://www.ntg.nl/mailman/listinfo/dev-context
