ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Most portable font name
Date: Fri, 18 May 2012 11:40:21 +0200	[thread overview]
Message-ID: <4FB61905.8070506@wxs.nl> (raw)
In-Reply-To: <20120518062018.GA11665@phlegethon>

On 18-5-2012 08:20, Philipp Gesang wrote:
> On 2012-05-18 00:00, Hans Hagen wrote:
>> On 17-5-2012 16:11, Philipp Gesang wrote:
>>
>>> 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*?
>>
>> For a project that has to run for a long time, I prefer filenames
>> (file:). When fonts are stable names can be used too and the name
>> resolved will check several names in the font. Spaces are ignored
>> and names are lowercases. There's also some fallback name
>> construction going on. Anyhow, the biggest problem is with fonts
>> that have the same names (but different files).
>
> I see. But even the filename can be treacherous: afair there is a
> times.ttf among the MS core fonts but it’s different from the one
> shipped with their office tools. The font name guessing, otoh,
> seems pretty elaborate, though I have not had the opportunity to
> look at it in detail.

I always put such fonts in tex/texmf-fonts/fonts/data so that I'm sure 
what gets used.

Hans




-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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-18  9:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-17 14:11 Philipp Gesang
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 [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=4FB61905.8070506@wxs.nl \
    --to=pragma@wxs.nl \
    --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).