RE: [ft-devel] issue with ArialMT in 2.1.9

[Ian Brown]

My assumption is that the font is in error and freetype is right. That's
not the issue though, at least not for me. My issue is that there is a
commonly distributed font out there which freetype used to deal with
okay, but in the latest release throws an error with. As the error is in
the space character, which doesn't have a glyph bitmap anyway, it would
be good if the error could be ignored so that freetype can continue to
deal with this font.
Also, when used on a postscript printer, the font does not give an error
- which gives my customers more ammunition to say that freetype is wrong
:(

Ian

-----Original Message-----
From: Werner LEMBERG [mailto:address@hidden 
Sent: 02 February 2005 22:20
To: Ian Brown
Cc: address@hidden
Subject: Re: [ft-devel] issue with ArialMT in 2.1.9

> 2 index /CharStrings 230 dict dup begin
> /space {
>       182 278 hsbw
>       0 0 vstem
>       0 0 hstem
>       0 hmoveto
>       closepath
>       endchar
>       } |-

Note that this is incorrect Type 1, according to the specification.
The first command after `hsbw', `vstem', and `hstem' in a glyph *must*
be `rmoveto', even if it is `0 0 rmoveto'.


    Werner