ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
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 23:11:03 +0100	[thread overview]
Message-ID: <54974577.3090807@gmx.es> (raw)
In-Reply-To: <op.xq8iyiw9p7eajd@muck.fritz.box>

On 12/21/2014 09:24 PM, j. van den hoff wrote:
> On Sun, 21 Dec 2014 19:22:22 +0100, Pablo Rodriguez wrote:
>> [...]
>> 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]
> 
> no, that does not work (despite it being listed by `mtxrun...fonts'. I  
> need to specify 'courier new' here.

I‘m afraid I cannot say why it doesn’t (all I know is that it should work.)

> but I'm already stumbling about the next thing. while playing around with
> some nice fonts I also tried out `optima' (like palatino by h. zapf).
> so that is what I see:
> 
> mtxrun --script font --list --all --name --pattern=*optima*
> 
> optima             optimaextrablack   /System/Library/Fonts/Optima.ttc    
> index:  0
> optimablack        optimaextrablack   /System/Library/Fonts/Optima.ttc    
> index:  0
> optimabold         optimabold         /System/Library/Fonts/Optima.ttc    
> index:  3
> optimabolditalic   optimabolditalic   /System/Library/Fonts/Optima.ttc    
> index:  1
> optimaextrablack   optimaextrablack   /System/Library/Fonts/Optima.ttc    
> index:  0
> optimaitalic       optimaitalic       /System/Library/Fonts/Optima.ttc    
> index:  2
> optimanormal       optimaitalic       /System/Library/Fonts/Optima.ttc    
> index:  2
> optimaregular      optimaregular      /System/Library/Fonts/Optima.ttc    
> index:  4
> 
> then, when using, e.g.,
> 
> \definefontfamily [mainface] [serif] [Optima]
> \definefontfamily [mainface] [sans]  [Optima]
> [...]
> neither \it nor \bf (italic and bold) variants are working in the body  
> text (but are just rendered
> in the regular \rm font). when using
> 
> \definefontfamily [mainface] [serif] [ebgaramond]
> 
> instead, \it _does_ work, while \bf is not available. _this_ I might  
> understand since there
> seems to be no bold variant of that font in the texlive distro (only  
> 'regular' and 'italic'.
> 
> but I would have thought that the different variants (italic, bold) can  
> always be expected to just work
> if they are present (as they are for `optima')?

Well, I’m afraid that I can only guess not having access to a MacOS
computer.

.ttc stands for TrueType collection, it isn’t actually a font. From what
I read at the wiki, dealing with .ttc is problematic (or at least, it
was in the past: http://wiki.contextgarden.net/Fonts_in_LuaTeX).

Sorry, I have never dealt with a .ttc file before. I have installed
Averia Serif and Sans TTC (http://iotic.com/averia/).

They seem to work:

\definefontfamily [mainface] [serif] [Averia Serif]
\definefontfamily [mainface] [sans] [Averia Sans]
\setupbodyfont[mainface]
\starttext
\startTEXpage[offset=1em]
{\rm a \em b \bf c \em d}

{\ss a \em b \bf c \em d}
\stopTEXpage
\stoptext

How about \definefontfamily [mainface] [serif] [Optima Regular]? Does it
switch fonts?

Just in case it helps,


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
___________________________________________________________________________________

      parent reply	other threads:[~2014-12-21 22:11 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
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 [this message]

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=54974577.3090807@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).