From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: typescripts
Date: Wed, 17 Mar 2010 13:34:34 +0100 [thread overview]
Message-ID: <4BA0CC5A.2070404@googlemail.com> (raw)
In-Reply-To: <54d7f5601003170516q76f5d740w1c789c31c2903b4@mail.gmail.com>
Am 17.03.10 13:16, schrieb Michael Saunders:
>> You can apply only *one* feature to \definefontfeatures.
>>
> I've seen examples like this:
> [...]
> so I think you mean to say that I can apply only one feature to
> \definefontsynonym or to \definetypeface.
Yes.
> I tried this and it checks out. Thanks---it's nice to see hz working.
> Protrusion is only on the right margin?
>
Left and right but quotation marks do not appear so often on the left
margin.
> (Also, I'm hoping that having a dozen different sets of font features won't
> require twelve times as many switches and feature names as this. I think
> there is some easier method for switching---Hans mentioned \addff{}, but
> I can't find anything in the docs. If that works, that would make two kinds
> of switches, one for some kinds of features and another for other kinds.)
>
\addff, \subff etc. are rather new commands and therefore only documented
in the source, you're free to add them to the wiki.
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
___________________________________________________________________________________
next prev parent reply other threads:[~2010-03-17 12:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 12:16 typescripts Michael Saunders
2010-03-17 12:34 ` Wolfgang Schuster [this message]
2010-03-18 0:04 ` typescripts Wolfgang Schuster
-- strict thread matches above, loose matches on Subject: below --
2010-11-12 14:32 typescripts Herbert Voss
2010-11-12 16:29 ` typescripts Herbert Voss
2010-11-12 16:54 ` typescripts Hans Hagen
2010-11-12 16:57 ` typescripts Hans Hagen
2010-11-12 17:41 ` typescripts Herbert Voss
2010-11-12 17:46 ` typescripts Hans Hagen
[not found] ` <4CDD80A7.7040803@FU-Berlin.DE>
[not found] ` <4CDD8246.2020206@wxs.nl>
2010-11-12 20:39 ` typescripts Herbert Voss
2010-11-10 18:57 typescripts Herbert Voss
2010-11-10 20:28 ` typescripts Mojca Miklavec
2010-11-10 21:14 ` typescripts Herbert Voss
2010-11-11 5:20 ` typescripts Wolfgang Schuster
2010-11-11 11:03 ` typescripts Mojca Miklavec
2010-11-11 11:27 ` typescripts Hans Hagen
2010-11-11 14:15 ` typescripts Mojca Miklavec
2010-03-18 20:42 typescripts Michael Saunders
2010-03-18 1:32 typescripts Michael Saunders
2010-03-18 9:53 ` typescripts Wolfgang Schuster
2010-03-18 10:04 ` typescripts Wolfgang Schuster
2010-03-17 1:26 typescripts Michael Saunders
2010-03-17 8:20 ` typescripts Wolfgang Schuster
2010-03-17 9:04 ` typescripts Mojca Miklavec
2010-03-17 9:11 ` typescripts Wolfgang Schuster
2010-03-17 11:33 ` typescripts Mojca Miklavec
2010-03-17 12:12 ` typescripts Wolfgang Schuster
2003-08-16 20:05 typescripts Henning Hraban Ramm
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=4BA0CC5A.2070404@googlemail.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).