ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "j. van den hoff" <veedeehjay@googlemail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: access to system fonts under MacOSX
Date: Sun, 21 Dec 2014 18:37:25 +0100	[thread overview]
Message-ID: <op.xq8a8nugp7eajd@muck.fritz.box> (raw)
In-Reply-To: <5496F351.70601@gmx.es>

On Sun, 21 Dec 2014 17:20:33 +0100, Pablo Rodriguez <oinos@gmx.es> wrote:

> On 12/21/2014 02:31 PM, j. van den hoff wrote:
>> On Sat, 20 Dec 2014 23:26:29 +0100, Pablo Rodriguez <oinos@gmx.es>  
>> wrote:
>>
>>> Hi Jörg,
>>> I don’t have a Mac, but this works in ConTeXt:
>>> \definefontfamily [mainface] [serif] [TeX Gyre Pagella]
>>> \definefontfamily [mainface] [sans]  [Helvetica]
>>> \definefontfamily [mainface] [mono]  [Courier]
>>> \definefontfamily [mainface] [math]  [TeX Gyre Pagella Math]
>>> \setupbodyfont[mainface]
>>
>> I've now looked a bit closer: this works (on my Mac) _except_ for
>> the teletype font: `\tt{some text}' ends up being typeset in the
>> serif font. `Courier' is there, for sure (meaning: it is listed by
>> `mtxrun --script font...' but it does not work. on closer inspection,
>> the actually found fontfiles are `courier new.ttf' and specifying
>> [couriernew] _does_ work.
>
> Hi Jörg,
>
> \tt is a switch, so the right way to deploy it is:
>
>    {\tt this text should be typewritten text}

yes, that's right.

>
> I have just discovered that Courier doesn’t work on my system either. I
> cannot find it.
>
> Could you give the output from the following command?
>
>     $ mtxrun --script font --list --name --pattern=courier*

sure:

courier                    courier                    pcrr8a.afm
courierbold                courierbold                pcrb8a.afm
courierboldoblique         courierboldoblique         pcrbo8a.afm
couriermedium              courier                    pcrr8a.afm
couriernew                 couriernewpsmt              
/Library/Fonts/Courier New.ttf
couriernewbold             couriernewpsboldmt          
/Library/Fonts/Courier New Bold.ttf
couriernewbolditalic       couriernewpsbolditalicmt    
/Library/Fonts/Courier New Bold Italic.ttf
couriernewitalic           couriernewpsitalicmt        
/Library/Fonts/Courier New Italic.ttf
couriernewnormal           couriernewpsitalicmt        
/Library/Fonts/Courier New Italic.ttf
couriernewpsbolditalicmt   couriernewpsbolditalicmt    
/Library/Fonts/Courier New Bold Italic.ttf
couriernewpsboldmt         couriernewpsboldmt          
/Library/Fonts/Courier New Bold.ttf
couriernewpsitalicmt       couriernewpsitalicmt        
/Library/Fonts/Courier New Italic.ttf
couriernewpsmt             couriernewpsmt              
/Library/Fonts/Courier New.ttf
couriernewregular          couriernewpsmt              
/Library/Fonts/Courier New.ttf
courieroblique             courieroblique             pcrro8a.afm

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.

>
>> 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.
>
>> or: _how_ exactly can fonts be specified? how is the mapping from
>> symbolic names to actual font files performed. it seems, sometimes
>> symbolic (short) names work, sometimes they don't. so, is there some
>> prescription, what is the right (TM) way to do it?>
>
> I think using full names is a good way to do it. But TeX Gyre Adventor
> comes with ConTeXt. You don’t have it installed on your system.

yes, that I know. they are part of the texlive distribution I use.

thanks for your help,

joerg
>
>
> Pablo


-- 
kUsing 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
___________________________________________________________________________________

  reply	other threads:[~2014-12-21 17:37 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 [this message]
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.xq8a8nugp7eajd@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).