ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: the new simplefonts stuff
Date: Thu, 4 Sep 2014 00:21:22 +0200	[thread overview]
Message-ID: <71C2E9A1-41FA-48B7-896C-6433A9B18D46@gmail.com> (raw)
In-Reply-To: <20140903214012.05e5de2d@medea1.site>


[-- Attachment #1.1: Type: text/plain, Size: 1480 bytes --]


Am 03.09.2014 um 21:40 schrieb Joshua Krämer <joshua.kraemer@gmail.com>:

> On 2014-09-01, 21:20, Sandra Snan wrote:
> 
>> This is probably a pretty basic question, but how do I find out the
>> name of the font that \definefontfamily expects in the third argument?
> 
> Hi Sandra,
> 
> the only reliable method I have found is to inspect the font with
> FontForge.
> 
> Here is an example: the Swiss 721 font from Bitstream (Helvetica
> digitization).
> 
> FontForge reports:
> 
> Font name:    Swiss721BT-Roman
> Family name:  Swis721 BT
> Display name: Swiss 721 BT
> Weight:       Book
> 
> "mtxrun --script fonts --list --all --pattern=swiss" result:
> 
> swiss721bt                  swiss721btroman             Swiss721.ttf
> swiss721btroman             swiss721btroman             Swiss721.ttf
> 
> The only name which works in ConTeXt is the family name (which can be
> seen in FontForge): "Swis721 BT", note the single "s".  However, this
> name is *not* shown in the mtxrun output.

Don’t expect logic in the internal names of a font, there is none.

> Interestingly, I have also seen mtxrun show the family name (different
> from the font name) for other fonts, so I really do not know how it
> makes up its output.  It is certainly not useful to find out the
> name that is to be used in ConTeXt.

The family name is shown when you use the info option, e.g.

mtxrun --script font --list --info --all texgyrepagella*

Wolfgang

[-- Attachment #1.2: Type: text/html, Size: 2498 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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-09-03 22:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-01 19:20 Sandra Snan
2014-09-02 14:16 ` Pablo Rodriguez
2014-09-03 19:40 ` Joshua Krämer
2014-09-03 22:21   ` Wolfgang Schuster [this message]
2014-09-03 20:51 ` Wolfgang Schuster
     [not found] <87wq9jrh44.fsf@ellen.idiomdrottning.org>
2014-09-04 15:53 ` Mica Semrick
2014-09-05  6:22   ` Sandra Snan
     [not found] ` <5D145AD1-28A8-491E-8601-DE1369F3E663@gmail.com>
2014-09-05  6:20   ` Sandra Snan
2014-09-05 10:19   ` Keith McKay

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=71C2E9A1-41FA-48B7-896C-6433A9B18D46@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).