ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: David Wooten <david.wooten@mac.com>
Subject: Re: Initial Font Installation Question (Mac)
Date: Fri, 11 Mar 2005 15:40:14 -0800	[thread overview]
Message-ID: <ca0656b63bee2929ff2256d08c2396d0@mac.com> (raw)
In-Reply-To: <4f1e51786a0426300cf3cf6ee324eccb@mac.com>

Greetings ConTeXters

I'm back to ask another question:
After an initial successful installation of the purchased fonts, I've 
come to find that there is a serious quirk. That is, when I try to use 
any special glyph, be it an accented character of any kind, or e.g. an 
eth. The result of something like \"a (or \"{a}) is _a_ without the 
diacritic. Curiously (to me, at least:), if I enter the actual glyph: 
ä, it gives me the character I need…but only for a few runs! After 
adding a couple more of such "alternative" glyphs, it starts to show 
gibberish. Some trials evince an ff-ligature as the diacritic. Errors 
in the mapping/virtual font/…?

Again I hope to save myself some time by asking to be pointed in the 
right direction, as my initial searches haven't really helped.

Kind Regards,
David Wooten

On Feb 21, 2005, at 1:17 AM, Adam Lindsay wrote:

> 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

  reply	other threads:[~2005-03-11 23:40 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
2005-02-25  3:34     ` David Wooten
2005-03-11 23:40       ` David Wooten [this message]
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=ca0656b63bee2929ff2256d08c2396d0@mac.com \
    --to=david.wooten@mac.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).