ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Adam Lindsay" <atl@comp.lancs.ac.uk>
Subject: Re: Initial Font Installation Question (Mac)
Date: Mon, 21 Feb 2005 09:17:11 +0000	[thread overview]
Message-ID: <20050221091711.28416@mail.comp.lancs.ac.uk> (raw)
In-Reply-To: <624cc25b73f0805f272779a6f64f63aa@uni-bonn.de>

Thomas A.Schmitz said this at Mon, 21 Feb 2005 10:01:50 +0100:

>Just a quick reply:
>
>having the afm is already very good. The file without an extension 
>looks suspiciously like a Mac font resource. Can you try running the 
>utility "fondu" on it (from the command line)? That will usually 
>produce the pfbs (very likely, there's more than one: roman, italics, 
>bold ...). Texfont, btw, can equally well work with truetype fonts, so 
>if you have a proper tryetype font with extension .ttf. you might as 
>well use this. texfont will produce a map entry that you will have to 
>modify a bit (so it points to a .ttf instead of the default .pfb), but 
>that's not too difficult. As to names: don't bother, ConTeXt is happy 
>with whatever name you throw at it.

Only a couple things to add:
When fondu generates the .pfb file, copy the .afm to share the new
(probably longer) filename.

Texfont on MacOSX trips on capital letter extensions: make sure they're
uniformly lower case.

If fondu fails you (it hasn't failed me yet), there's also t1unmac (lcdf.org).

And if texfont installation fails or inexplicably stalls, you might need
to go in and truncate long (255+ character) lines by manually editing the
text file. I've always found these to be comment/copyright lines, so
you're not hurting anything by doing so.

You lucky so-and-so for getting Andulka!
adam

>On Feb 21, 2005, at 1:58 AM, David Wooten wrote:
>
>> Greetings all,
>>
>> I've been having a lot of fun struggling with the installation of a 
>> newly purchased font, and wanted to double check a preliminary 
>> question before I give in and ask a more thorough question ;)
>>
>> I'm working with Mac OS X, so I bought a font-set with both Mac TTF 
>> and Postscript files. The Postscript folders have 2 types of file for 
>> each fontname: .afm and another without a suffix. The names also have 
>> uppercase letters, such as AndulBooBol (a.k.a. Andulka Book Bold).
>>
>> For the texfont script, it apparently needs the .afm files and .pfb 
>> files. Thus:
>>
>> 1) Are these non-suffixed files the .pfb files in question? If so, 
>> should I rename (add .pfb to) them before trying to install them? (I 
>> could convert the TTF files to .pfb?)
>>
>> 2) Should I take away the UpperCaseLettering as well? Rename them to 
>> something more Berry-like?
>>
>> In fact, I've tried these things with no success, but before I spell 
>> out the details of my failure I thought I would get this straight.
>>
>> Kind regards,
>> David Wooten
>>
>> _______________________________________________
>> ntg-context mailing list
>> ntg-context@ntg.nl
>> http://www.ntg.nl/mailman/listinfo/ntg-context
>>
>
>_______________________________________________
>ntg-context mailing list
>ntg-context@ntg.nl
>http://www.ntg.nl/mailman/listinfo/ntg-context

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Adam T. Lindsay, Computing Dept.     atl@comp.lancs.ac.uk
 Lancaster University, InfoLab21        +44(0)1524/510.514
 Lancaster, LA1 4WA, UK             Fax:+44(0)1524/510.492
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2005-02-21  9:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-21  0:58 David Wooten
2005-02-21  9:01 ` Thomas A.Schmitz
2005-02-21  9:17   ` Adam Lindsay [this message]
2005-02-25  3:34     ` David Wooten
2005-03-11 23:40       ` David Wooten
2005-03-11 23:55         ` Adam Lindsay
2005-03-12 21:49         ` Adam Lindsay
2005-03-12 23:07           ` David Wooten
2005-03-12 23:58             ` Adam Lindsay
2005-03-13  0:31               ` David Wooten
2005-03-13 18:48         ` h h extern

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=20050221091711.28416@mail.comp.lancs.ac.uk \
    --to=atl@comp.lancs.ac.uk \
    --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).