From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: doublestroke
Date: Sun, 22 Dec 2013 17:40:17 +0100 [thread overview]
Message-ID: <4AB6B484-F64A-4407-9742-A6635E51B45F@gmail.com> (raw)
In-Reply-To: <CAGMMSTB5+r60cdFTiFR7XZ3fHGtv6fhDFoDGBW3=oihqHoqhDw@mail.gmail.com>
Am 22.12.2013 um 17:33 schrieb Elspeth McGullicuddy <elspethmcgullicuddy@gmail.com>:
> I've done the install with the script and it worked just out of the box.
>
> I've found all the sources I was looking for (pity (or not), they are
> not indexed by google).
>
> I've made this tiny change to have the behavior I was looking for:
>
> \definefontfamily [mainface] [rm] [Latin Modern Roman]
>
> \definefallbackfamily [mainface] [mm] [TeX Gyre Termes Math] [range=uppercasedoublestruck] [force=no]
The “range” and “force” settings have to be set in the same argument and even then I don’t think
you want “force=no” because this would take the glyphs from Latin Modern and your fallback
font is ignored.
The purpose of the “force” and “check” keys is explained in the source for the fallback mechanism:
% check : only replace when present in replacement font (default: no)
% force : force replacent even when basefont has glyph (default: yes)
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:[~2013-12-22 16:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 15:50 doublestroke Elspeth McGullicuddy
2013-12-22 1:47 ` doublestroke Elspeth McGullicuddy
2013-12-22 3:10 ` doublestroke Elspeth McGullicuddy
2013-12-22 10:56 ` doublestroke Wolfgang Schuster
2013-12-22 13:12 ` doublestroke Elspeth McGullicuddy
2013-12-22 13:28 ` doublestroke Wolfgang Schuster
2013-12-22 14:09 ` doublestroke Elspeth McGullicuddy
2013-12-22 14:15 ` doublestroke Wolfgang Schuster
2013-12-22 15:23 ` doublestroke Elspeth McGullicuddy
2013-12-22 15:49 ` doublestroke Wolfgang Schuster
2013-12-22 16:33 ` doublestroke Elspeth McGullicuddy
2013-12-22 16:40 ` Wolfgang Schuster [this message]
2013-12-22 17:06 ` doublestroke Elspeth McGullicuddy
2013-12-22 17:23 ` doublestroke Wolfgang Schuster
2013-12-22 17:29 ` doublestroke Elspeth McGullicuddy
2013-12-26 0:01 ` doublestroke Elspeth McGullicuddy
2013-12-26 8:09 ` doublestroke Wolfgang Schuster
2013-12-26 11:57 ` doublestroke Hans Hagen
2013-12-26 15:13 ` doublestroke Elspeth McGullicuddy
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=4AB6B484-F64A-4407-9742-A6635E51B45F@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).