From: S Barmeier <severinbarmeier@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Multiple font fallbacks
Date: Mon, 02 Apr 2012 10:31:55 +0900 [thread overview]
Message-ID: <4F79018B.7040508@googlemail.com> (raw)
I tried
\definefontfallback[fallback1]
\definefontfallback[fallback2]
and then
\definefontsynonym[][][fallbacks={fallback1,fallback2}]
and failed. What is the correct syntax?
Thank you,
Severin
___________________________________________________________________________________
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 reply other threads:[~2012-04-02 1:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 1:31 S Barmeier [this message]
2012-04-02 3:30 ` Wolfgang Schuster
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=4F79018B.7040508@googlemail.com \
--to=severinbarmeier@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).