[Bug 10660] New versions of Fontforge generate marlett. ttf with incorrect available character sets field

[wine-bugs at winehq.org]

http://bugs.winehq.org/show_bug.cgi?id=10660





--- Comment #20 from Stephan Wezel <s.wezel at web.de>  2008-02-07 21:31:37 ---
here is the last response of my question from George Williams:

George Williams wrote:
> Stephan Wezel wrote:
> > Currently they still thinking it isn't a wine bug but an bug in
> > fontforge. But when you say that the old behaviour on which the wine
> > build system currently relies was wrong then i will report it on the
> > mentioned wine bugreport.
>
> That is correct.
>
> I had assumed that adobe's symbol encoding (which is what "symbol" means
> inside fontforge) was the same as Microsoft's 3,0 cmap entry. It is not.
> I presume that they made the same mistake, aided in doing so by my
> mistake.
>
> In my opinion, marlett.sfd is erroneous. It claims an adobe symbol
> encoding, which it does not, in fact, have. I don't think that could be
> created with fontforge, I think someone must have hand edited the file
> to produce that peculiar melange.

So it seems really a bug in the wine build-system part which generates the
font.
Because it relays on a behavior of fontforge which was incorrect. 


-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.