From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: access to system fonts under MacOSX
Date: Sun, 21 Dec 2014 19:22:22 +0100 [thread overview]
Message-ID: <54970FDE.20808@gmx.es> (raw)
In-Reply-To: <op.xq8a8nugp7eajd@muck.fritz.box>
On 12/21/2014 06:37 PM, j. van den hoff wrote:
> On Sun, 21 Dec 2014 17:20:33 +0100, Pablo Rodriguez wrote:
>> On 12/21/2014 02:31 PM, j. van den hoff wrote:
> [...]
> as I wrote in the last mail, only the `courier new' fonts are
> represented by actual font-files it seems (don't know what the *afm
> files are). so if only those (and their abbreviations) were reported
> I would not have any problem. but as it stands, `courier' is
> reported as well -- but does not map to any actual font-file.
.afm is an Adobe font metrics file. This is the way (old) PostScript
fonts are designed. Font glyphs in PostScript fonts are cotained in .pfa
or .pfb files.
Wikipedia has a good article explaining PostScript fonts
(https://en.wikipedia.org/wiki/PostScript_fonts). But unless you have an
special interest, I’d simply ignore it.
If I‘m not wrong, only system font files are listed with their path. The
fonts that come with ConTeXt are listed, but their paths are ignored.
BTW, this should work (if I’m not completely wrong [it doesn’t work on
my system, because the courier fonts aren’t listed]):
\definefontfamily [mainface] [tt] [courier]
>>> so it seems you are right regarding using the "full" names, e.g.
>>>
>>> \definefontfamily [mainface] [sans] [adventor]
>>>
>>> does not work while
>>>
>>> \definefontfamily [mainface] [sans] [TeX Gyre Adventor]
>>>
>>> does.
>>>
>>> any ideas, why all this is happening?
>>
>> \definefontfamily [mainface] [sans] [texgyreadventor]
>>
>> seems to be the right way to invoke the font.
Sorry, I’m afraid my explanation was incomplete.
adventor is the name of a(n already predefined) typescript. So you can
use it with \setupbodyfont and \switchtobodyfont.
texgyreadventor is the name of the typeface or font family. You should
use it with \definefontfamily.
But typefaces cannot be invoked with typescript names and typescripts
cannot be invoked with typeface names.
This is why \definefontfamily[mainface][sans][adventor] or
\setupbodyfont[texgyreadventor] don’t work.
Wolfgang will know that better, but [mainface] in the previous
\definefontfamily is the new and easy way to create typescripts in ConTeXt.
Using the full font name has the main advantage of not having to know
whether a given name designs a typescript or a typeface ;-).
I hope it will be clearer now. Let me know if it isn’t.
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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:[~2014-12-21 18:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-20 18:31 j. van den hoff
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 [this message]
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=54970FDE.20808@gmx.es \
--to=oinos@gmx.es \
--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).