ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Khaled Hosny <khaledhosny@eglug.org>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: (RSFS) font installation
Date: Fri, 18 Mar 2011 05:27:10 +0200	[thread overview]
Message-ID: <20110318032710.GB7791@khaled-laptop> (raw)
In-Reply-To: <C3CA1689-10AB-46DB-A17A-25BDF2C55970@pobox.com>

On Thu, Mar 17, 2011 at 09:42:38PM -0500, mathew wrote:
> > - If the .pfm and .pfb files are sufficient for Windows, why does
> > mtxrun specifically search for .afm files and not also for .pfm?
> 
> Probably because mtxrun (and the rest of ConTeXt and LuaTeX) are
> written for Unix and ported to Windows, and Unix uses .afm files for
> metrics. (Except OS X, which is different for historical reasons.)
> 
> That and .afm files are much easier to work with because they're text
> files.

AFAIK, ConTeXt needs afm files to load type1 files, something related to
encoding the font and ligatures/kerning. So you need bot afm and bfb/bfa
files together somewhere context searches for fonts and it should work.
PFM files are not needed at all (dunno what they are for actually, some
obscure windows thing I guess).

> But it might not be a bad idea for LuaTeX to automatically perform a
> pfm2afm conversion and cache the converted files when necessary, and
> probably not that hard to code. On the other hand, Type 1 fonts are
> legacy at this point, so it might not be worth it.

LuaTeX can load afm files thanks to the embedded, fontforge derived,
font loader, but AFAIK it does not handle pfm files at all.

Hans considers type1 fonts obsolete (and I agree with him :)) and he is
unlikely to put much effort into supporting them.

Regards,
 Khaled

-- 
 Khaled Hosny
 Egyptian
 Arab
___________________________________________________________________________________
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:[~2011-03-18  3:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-16 14:00 Stefan Müller
2011-03-16 15:58 ` mathew
2011-03-17  9:05   ` Stefan Müller
2011-03-17 12:40     ` Ulrike Fischer
2011-03-17 13:41       ` Stefan Müller
2011-03-17 16:12         ` Otared Kavian
2011-03-17 16:53           ` Stefan Müller
2011-03-17 15:04     ` mathew
2011-03-17 16:53       ` Stefan Müller
2011-03-18  2:42         ` mathew
2011-03-18  3:27           ` Khaled Hosny [this message]
2011-03-18 10:04             ` Hans Hagen
2011-03-18 14:40               ` mathew
2011-03-18 14:51                 ` Hans Hagen
2011-03-18 16:01                   ` mathew
2011-03-18 18:30                     ` Hans Hagen
     [not found]                       ` <AANLkTinWPdN-H6TPNato9PG7Fh0PzvfS0PkHXehzbt6J@mail.gmail.com>
2011-03-22 16:08                         ` mathew
2011-03-22 16:55                           ` Taco Hoekwater
2011-03-18 11:26           ` Stefan Müller
2011-03-18 11:39             ` Hans Hagen
2011-03-18 14:47               ` Stefan Müller

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=20110318032710.GB7791@khaled-laptop \
    --to=khaledhosny@eglug.org \
    --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).