Comment 40 for bug 199331

I believe that I did everything I could do from Wine point of view:
I described what and where the problem is. Now it's just up to fontforge
developer(s) to make .sfd -> .ttf (and probably .ttf -> .sfd) font generation
work properly without any external hacks like proposed file extensions, since
that apparently doesn't allow to create fonts with Symbol and some other
unicode range bits set in ulCodePageRange1.

If "Encoding: Symbol" is really wrong in marlett.sfd, let's remove it, but
we need a working solution/replacement which works, and preferably works
with old, current and new fontforge versions.