From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Using Postscript Type 1 fonts in ConTeXt/XeTeX?
Date: Mon, 3 Mar 2008 17:44:23 +0100 [thread overview]
Message-ID: <6faad9f00803030844ye221619w7eada2ed592b4fa3@mail.gmail.com> (raw)
In-Reply-To: <AFC930D8-EE7F-4B05-861A-7F7AB65E117A@fiee.net>
On Sun, Mar 2, 2008 at 8:37 PM, Henning Hraban Ramm wrote:
> Some of your statements seem wrong or at least confusing to me:
>
> Am 2008-03-01 um 13:19 schrieb Roland:
>
>
> > 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.
>
> As you state later, all data fork fonts (TrueType, OpenType and
> PostScript) should work.
> For I never tried XeTeX I don't know if PS Type 1 and 3 will work.
They do. But the mac Type1 fonts come in some weird format for which
Jonathan hasn't written support in xdvipdfmx (yet). With xdv2pdf they
work OK.
> Isn't it possible to use traditional TeX-installed fonts with XeTeX?
Yes, it is. But the font that Roland has bought and is trying to use
in XeTeX comes in two flavors: one for mac (that's the one he has) and
one for Windows.
The "traditional TeX-installed" fonts are in the format that Windows
uses (another font, actually) and would not work in other Mac
applications. He would actually need either:
- the windows version of that font (which he doesn't have)
- or a patch for XeTeX (xdvipdfmx actually) that would allow him to
use the font he has (the patch *might* come one day, but there are
more important things in XeTeX waiting to be implemented)
- or to patch ConTeXt to use xdv2pdf instead of xdvipdfmx + rewrite a
bunch of definitions that load Latin Modern (they should not be loaded
since xdv2pdf doesn't support "traditional TeX-installed fonts")
- or to convert the font to some other format (officially forbidden, I guess)
The second problem is also that the syntax to call that font might
need to be changed, but that's a minor problem.
A story learned: it is possible, but any of the described ways is
extremely clumsy to use, so one should better use another font to
avoid problems.
Mojca
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2008-03-03 16:44 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
2008-03-02 14:21 ` Jérome Laurens
2008-03-02 19:37 ` Henning Hraban Ramm
2008-03-03 16:44 ` Mojca Miklavec [this message]
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=6faad9f00803030844ye221619w7eada2ed592b4fa3@mail.gmail.com \
--to=mojca.miklavec.lists@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).