From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \typescriptthree within the optional argument of \definefontsynonym
Date: Thu, 04 Aug 2016 15:43:43 +0200 [thread overview]
Message-ID: <57A3468F.4010609@gmail.com> (raw)
In-Reply-To: <CAMHZ1dY+DFcM_q=xqJxwNKDF__6cbK+B9rQb+kpLm3kr83W2tQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1724 bytes --]
> Mohammad Hossein Bateni <mailto:bateni@gmail.com>
> 4. August 2016 um 15:24
> Hello Hans,
>
> Suppose you have a typescript as follows.
>
> \starttypescript [first] [MyFont] [GoodieOne,GoodieTwo]
> \definefontsynonym [Serif] [\typescripttwo] [goodies=\typescriptthree]
> \stoptypescript
>
> Using macros \typescriptX (for X=one, two, and three) works in the
> first and second arguments in \definefontsynonym but not in the
> optional argument. This seems to be because the optional argument is
> not expanded. Is this a bug or a feature?
>
> What I want to do was have a set of "fixes" (correcting kern issues,
> etc.) for a collection of fonts. I can either put these in separate
> goodie files or feature sets (the latter being what I was trying but
> not in the sample above), and write generic typescripts that would
> load any of the fonts with its associated fixes.
>
> While I can use sans/serif/mono in the first argument, and name of the
> font in the second argument (to be mapped appropriately using
> \typescriptprefix to nmemonic name and real font name), the third
> (optional) argument of \definefontsynonym does not expand immediately,
> hence I'll end up with "undefined" \typescriptthree when it will be used.
You can try to expand the value of \typescripthree with
\starttypescript[...][...][...]
\expanded{\definefontsynonym[...][...][goodies=\typescriptthree]}
\expanded{\definefontsynonym[...][...][goodies=\typescriptthree]}
\stoptypescript
or
\starttypescript[...][...][...]
\startexpanded
\definefontsynonym[...][...][goodies=\typescriptthree]
\definefontsynonym[...][...][goodies=\typescriptthree]
\stopexpanded
\stoptypescript
Wolfgang
[-- Attachment #1.2: Type: text/html, Size: 2910 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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:[~2016-08-04 13:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-04 13:24 Mohammad Hossein Bateni
2016-08-04 13:43 ` Wolfgang Schuster [this message]
2016-08-04 14:00 ` Mohammad Hossein Bateni
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=57A3468F.4010609@gmail.com \
--to=schuster.wolfgang@gmail.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).