freetype-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Devel] Possible bug in ftxpost.c ?


From: Antoine Leca
Subject: Re: [Devel] Possible bug in ftxpost.c ?
Date: Mon, 08 Jul 2002 15:59:10 +0200

Bonjour Jean-Christophe,

En Jean-Christophe Dubacq va escriure:
> 

Sorry for the delay, I am not presently actively supporting FT1 because
I am switching OSes, and furthermore I did miss your post on Wenesday.

> I think ftxpost.c is wrong when reading the post table of a ttf font in
> format 0x00020000.

Looks like you are correct.


<snip> 
> Suppose we have a font with all standard glyphs, and three more glyphs
> /foo, /mud and /bar.
> 
> The table could look like the following (the first 261 is the number of
> names):
> <261><0><1>...<257><259><260><258> followed by the pascal strings:
> <3>foo<3>mud<3>bar
> 
> In the current code, glyph #259 would be called /foo, glyph #260 would
> be called /mud and glyph #258 would be called /bar. However, according
> to the TT reference manual (@developers.apple.com) and according to pdftex,
> the correct interpretation should be:
> glyph #258 has name index 259, therefore has name mud
> glyph #259 has name index 260, therefore has name bar
> glyph #260 has name index 258, therefore has name foo.

That is my reading of the specs too, and indeed our current code is wrong
(take a track that appears sometimes too short).

<snip> 
> I am trying to understand fully how to transfer TTF fonts in TeX and
> pdfTeX. There are various bugs along the road,

Please report them as soon as you found them (if they are related in any
way with Freetype), there are quite a number of gentlemen here that may
give you a hand (as time permits), and we all are certainly seeking
improving the general quality of these softwares.

> and one of them was the
> following: using the perfectly well known Impact font (from Monotype
> foundry, distributed for free by Microsoft), I found that the Euro glyph
> was mapped by ttf2tfm to some other char.

Indeed, Impact (version I use is 2.35 last modified November 6th 1998,
19:22:52) exhibits a bad behaviour: glyph 189 (a cheap and ugly Euro-like
done with capital C with two bars added) is shown in FTZOOM as "francxxx",
which is the PSname for glyph 247; likewise, glyph 247 is named "dmacron",
really the PSname for glyph 257; and all glyphs after 257 till 659 have
PSname's which are off by 1.


Thanks for the report. I will further investigate for a correction.

Antoine





reply via email to

[Prev in Thread] Current Thread [Next in Thread]