From: Khaled Hosny <khaledhosny@eglug.org>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Postscript Type1 fonts & MK IV
Date: Mon, 30 Aug 2010 11:38:14 +0200 [thread overview]
Message-ID: <20100830093814.GA1970@khaled-laptop> (raw)
In-Reply-To: <20100830061718.GA579@s70206.gridserver.com>
On Sun, Aug 29, 2010 at 11:17:18PM -0700, John Magolske wrote:
> * Khaled Hosny <khaledhosny@eglug.org> [100829 08:37]:
> > On Sat, Aug 28, 2010 at 11:50:38PM -0700, John Magolske wrote:
> > >
> > > Also, the SabonLT-Roman.afm file that came from Linotype has a section
> > > titled "StartKernData", but .afm files generated using type1afm,
> > > fontforge, font2afm, etc. have no kerning section. Would using such
> > > .afm files cause sub-standard output with regard to kerning?
> >
> > FontForge can load mac type1 kerning, see:
> > http://fontforge.sourceforge.net/faq.html#FOND-kern
>
> Thanks, useful information linked there:
>
> "The mac stored kerning information in the FOND resource associated
> with a bitmap font (it is not stored in the file with the postscript
> font). If you wish kerning data for a mac postscript font, you must
> find a font file containing a bitmap font with the same family and
> style as the postscript."
>
> Reading this, I went into the directory of the font in question,
> found the *.bmap file and ran `fondu -afm` on it. This created afm files
> for all the fonts in that family, each file including a "StartKernData"
> section with plenty of kerning data.
>
> So I feel closer...at least I know how to create afm files that
> include kerning data. But unfortunately, I still can't get these
> fonts to work with ConTeXt. It must have something to do with the
> font itself, as the SabonLT-Roman.afm and SabonLT-Roman.pfb I placed
> in the ~/.fonts directory are working fine.
Try Taco's suggestion, I myself got unpredictable results with ~/.fonts,
try instead ~/texmf/fonts/{afm,type1} or even ~/texmf/fonts/data
Regards,
Khaled
--
Khaled Hosny
Arabic localiser and member of Arabeyes.org team
Free font developer
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2010-08-30 9:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-27 23:16 John Magolske
2010-08-28 2:59 ` Wolfgang Schuster
2010-08-28 8:30 ` Hans Hagen
2010-08-29 6:50 ` John Magolske
2010-08-29 7:17 ` Taco Hoekwater
2010-08-29 8:11 ` John Magolske
2010-08-29 8:15 ` Taco Hoekwater
2010-08-29 8:23 ` Khaled Hosny
2010-08-30 6:17 ` John Magolske
2010-08-30 9:38 ` Khaled Hosny [this message]
2010-08-31 6:27 ` Postscript Type1 fonts & MK IV - [SOLVED] John Magolske
2010-08-31 7:31 ` Taco Hoekwater
2010-08-31 9:19 ` Taco Hoekwater
2010-08-31 11:20 ` Khaled Hosny
2010-08-31 15:35 ` Aditya Mahajan
2010-08-31 11:22 ` Khaled Hosny
2010-09-02 5:52 ` John Magolske
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=20100830093814.GA1970@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).