From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Proper setting of font features for protrusion/expansion
Date: Mon, 05 May 2014 00:36:19 +0200 [thread overview]
Message-ID: <5366C0E3.9000002@wxs.nl> (raw)
In-Reply-To: <00b201cf67d9$4a610470$df230d50$@tosovsky@email.cz>
On 5/4/2014 10:41 PM, Jan Tosovsky wrote:
> On 2014-05-04 Wolfgang Schuster wrote:
>> Am 04.05.2014 um 19:34 schrieb Jan Tosovsky:
>>
>>> In my code I use the following shortcut found somewhere:
>>>
>>> \definefontfamily[palatino][rm][Palatino Linotype][features={default,
>>> quality}]
>>>
>>> Is there any description what that '[features={default, quality}]'
>>> option really does?
>>
>> When you apply features to a font you can set a list of features and
>> all of them will be applied.
>>
>> In the example below you can see both methods, the first text uses the
>> new featurelist "testfeature" which uses "default" and extends it with
>> "protrusion=quality". The second text applies the two predefined lists
>> "default" and "quality" (which sets "protrusion=quality"
>> and "expansion=quality").
>>
>> \definefontfeature[testfeature][default][protrusion=quality]
>> ...
>> \startfont[Serif*testfeature]
>> ...
>> \startfont[Serif*default,quality]
>
> Aahh, thanks.
>
> So it is the preset name what confused me here... From my POV the 'quality'
> should be replaced with the more specific label. I believe it will enhance
> readability the code. I can imagine even 'microtypography' for this kind of
> preset.
quality is just a tag for a preset ... on can add his/her own
btw, i have no clue what micro or typography is involved (esp when
excessive values are used) ,,, using that term for a preset would be
rather confusing
> Jan
>
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
>
--
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2014-05-04 22:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53667a5e.c6cf0e0a.6333.339eSMTPIN_ADDED_BROKEN@mx.google.com>
2014-05-04 19:39 ` Wolfgang Schuster
2014-05-04 20:41 ` Jan Tosovsky
[not found] ` <00b201cf67d9$4a610470$df230d50$@tosovsky@email.cz>
2014-05-04 22:36 ` Hans Hagen [this message]
2014-05-04 17:34 Jan Tosovsky
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=5366C0E3.9000002@wxs.nl \
--to=pragma@wxs.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).