ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Philipp Gesang <gesang@stud.uni-heidelberg.de>
To: ConTeXt ML <ntg-context@ntg.nl>
Subject: Most portable font name
Date: Thu, 17 May 2012 16:11:58 +0200	[thread overview]
Message-ID: <20120517141158.GD8659@phlegethon> (raw)


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

Hi all,

tl;dr: by which name to refer to a font.

I was about to recommend (tomorrow; context: an introductory
LaTeX course) *the* way of referring to a font by its name. As we
all know, the same font (as in file) usually comes with a variety
of possible denominations. “otfinfo -i” on a *file name* results
in a list of *full name*, *Postscript name*, *unique id*, etc.,
which all might have some valid purpose. I have come across
answers to assignments that made me wonder “How on earth did E
get that to work on Eir system?”.  There’s some background info
[1] on the Fontforge pages but it doesn’t really answer my
question:

  Which identifier is least likely to break things and at the
  same time most portable between both frontends (Fontspec,
  Simplefonts, typescripts) and platforms (Win/Linux/Mac)?

For some time now I myself settled for the Postscript name as it
never caused problems in typescripts and it’s got no spaces. The
filename might be the most explicit one, but oftentimes contains
spaces which I *always* replace with underscores prior to
installing a font; also case insensitive filesystems might cause
trouble. Also, some fonts have weird file naming schemes (e.g.
CMU and the Paratype fonts), so extra comments may be required to
support legibility of the resulting code. The typescripts that
come with Context use both (“name:” and “file:”) but I have no
clue why exactly which method was chosen over the other in what
case.  The fontspec documentation (and the Simplefonts module and
our course so far) conforms to the WYSIWYG tradition of
purportedly more human-readable, spaced identifiers, e.g. “TeX
Gyre Bonum Bold”. (Cf. [1]: “FullName is designed to be read by
humans”.)

So I judged that my preferred choice might not be as good as I
think. I got cold feet and am about to remove the slide where I
recommend the PS name (I can do that later anyways). Is there --
apart from personal opinions -- some valid reason to prefer one
name over the other *in general*?

Thanks for any advice and opinions.

Philipp

[1] http://fontforge.sourceforge.net/fontinfo.html#Names


[-- Attachment #1.2: Type: application/pgp-signature, Size: 198 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:[~2012-05-17 14:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-17 14:11 Philipp Gesang [this message]
2012-05-17 22:00 ` Hans Hagen
2012-05-17 22:16   ` Bill Meahan
2012-05-17 22:22     ` Hans Hagen
2012-05-18  6:20   ` Philipp Gesang
2012-05-18  9:40     ` Hans Hagen

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=20120517141158.GD8659@phlegethon \
    --to=gesang@stud.uni-heidelberg.de \
    --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).