From: Thomas A.Schmitz <thomas.schmitz@uni-bonn.de>
Subject: Re: Initial Font Installation Question (Mac)
Date: Mon, 21 Feb 2005 10:01:50 +0100 [thread overview]
Message-ID: <624cc25b73f0805f272779a6f64f63aa@uni-bonn.de> (raw)
In-Reply-To: <b2caec9707cfd148dc9e8aee824b470a@mac.com>
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.
HTH
Thomas
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
>
next prev parent reply other threads:[~2005-02-21 9:01 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 [this message]
2005-02-21 9:17 ` Adam Lindsay
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=624cc25b73f0805f272779a6f64f63aa@uni-bonn.de \
--to=thomas.schmitz@uni-bonn.de \
--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).