From: "j. van den hoff" <veedeehjay@googlemail.com>
To: "ntg-context@ntg.nl" <ntg-context@ntg.nl>
Subject: access to system fonts under MacOSX
Date: Sat, 20 Dec 2014 19:31:35 +0100 [thread overview]
Message-ID: <op.xq6i2xrpp7eajd@muck.fritz.box> (raw)
newbie question:
how can I get access to fonts installed outside the TeX tree under MacOSX
(10.9 to be precise)?
mtxrun --script font --list --name --pattern=*
shows lots of fonts (so they are recognized by context, I'd guess)
but the simple-minded approach, namely to trying something like
\starttypescript [stix]
\definetypeface [stix] [rm] [serif] [stix] [default]
\definetypeface [stix] [ss] [sans] [adventor] [default]
\definetypeface [stix] [tt] [mono] [cursor] [default]
\definetypeface [stix] [mm] [math] [stix] [default]
\stoptypescript
\usetypescript[stix]
\setupbodyfont[stix,12pt]
fails with `unknown library stix'.
obviously I am doing something wrong -- or is this a luatex problem not
being able to find the system fonts?
thx, joerg
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
___________________________________________________________________________________
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:[~2014-12-20 18:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-20 18:31 j. van den hoff [this message]
2014-12-20 22:26 ` Pablo Rodriguez
2014-12-21 10:51 ` j. van den hoff
2014-12-21 16:01 ` Pablo Rodriguez
2014-12-21 13:31 ` j. van den hoff
2014-12-21 16:20 ` Pablo Rodriguez
2014-12-21 17:37 ` j. van den hoff
2014-12-21 18:22 ` Pablo Rodriguez
2014-12-21 20:24 ` j. van den hoff
2014-12-21 21:39 ` Wolfgang Schuster
2014-12-21 21:45 ` j. van den hoff
2014-12-21 21:56 ` Wolfgang Schuster
2014-12-21 22:23 ` j. van den hoff
2014-12-21 23:12 ` j. van den hoff
2014-12-22 6:09 ` Pablo Rodriguez
2014-12-23 13:19 ` j. van den hoff
2014-12-22 21:35 ` Loading modules (was: access to system fonts under MacOSX) Wolfgang Schuster
2014-12-23 13:15 ` j. van den hoff
2014-12-23 13:29 ` Loading modules Wolfgang Schuster
2014-12-23 13:29 ` Loading modules (was: access to system fonts under MacOSX) j. van den hoff
2014-12-23 13:38 ` Loading modules Wolfgang Schuster
2014-12-21 22:17 ` access to system fonts under MacOSX Pablo Rodriguez
2014-12-21 22:22 ` j. van den hoff
2014-12-21 22:11 ` Pablo Rodriguez
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=op.xq6i2xrpp7eajd@muck.fritz.box \
--to=veedeehjay@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).