ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Roland <ntg-context@rolandsiebelink.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Using Postscript Type 1 fonts in ConTeXt/XeTeX?
Date: Sat, 1 Mar 2008 13:19:46 +0100	[thread overview]
Message-ID: <cd7ae9e30803010419s316804cy4e63628f3bd8ca18@mail.gmail.com> (raw)
In-Reply-To: <cd7ae9e30802010011i4227188fwee641ad6da7efb61@mail.gmail.com>

Seems we never posted the conclusion about this problem: XeTeX simply
doesn't work with the old Mac Type 1 Postscript fonts on Mac OS X
(Leopard or before). The reason is that these old fonts store their
data in the resource fork, which Unix utilities like XeTeX don't see.
Only TrueType or OpenType fonts will be recognised and loaded
correctly.

PCs don't have the data fork so old Type 1 Postscript fonts for PCs
(with .pfb extension) seem to work. Just copying these to the Mac is
no solution, however, because Mac OS X does not support PC-style Type
1 fonts (only the Mac ones with the data in the resource fork), and
therefore XeTeX will not find these fonts.

Therefore the preferred solution is to use fonts of TrueType or
OpenType varieties. For those with access to a font conversion program
like fondu (?) fontforge (?) or fontlab (?) it may be possible to
convert the old Type 1 font to TrueType or OpenType, reinstall it and
have XeTeX work with it in that way.
___________________________________________________________________________________
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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  parent reply	other threads:[~2008-03-01 12:19 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-20 10:21 Roland
2008-01-20 12:54 ` Wolfgang Schuster
2008-01-20 16:40   ` Mojca Miklavec
2008-01-20 17:37     ` Mojca Miklavec
     [not found]       ` <cd7ae9e30801201252k239a94cdteac2368f3b0cc45f@mail.gmail.com>
2008-01-20 20:55         ` Roland
2008-01-20 21:11           ` Mojca Miklavec
2008-01-21  7:22             ` Roland
2008-01-21 10:49               ` Mojca Miklavec
2008-01-21 23:00                 ` Roland
2008-01-21 23:39                   ` Mojca Miklavec
2008-01-22  6:44                     ` Roland
2008-01-22  8:37                       ` Mojca Miklavec
2008-02-01  8:09                         ` Roland
     [not found]                           ` <cd7ae9e30802010011i4227188fwee641ad6da7efb61@mail.gmail.com>
2008-03-01 12:19                             ` Roland [this message]
2008-03-02 14:21                               ` Jérome Laurens
2008-03-02 19:37                               ` Henning Hraban Ramm
2008-03-03 16:44                                 ` Mojca Miklavec
2008-03-03 19:58                                   ` Henning Hraban Ramm
2008-03-04  0:10                                     ` Mojca Miklavec
2008-03-04  0:16                                       ` Wolfgang Schuster
2008-01-20 20:48   ` Roland

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=cd7ae9e30803010419s316804cy4e63628f3bd8ca18@mail.gmail.com \
    --to=ntg-context@rolandsiebelink.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).