Hello !

It does look like the bug has been fixed both in mftrace and in fontforge, which is great, thanks !

        Vincent Fourmond


I've just tried reproducing the bug reported below with version 1.0.34-1 and 1.1.3-1 (as yet unreleased) and have had no success.

Do you still find that this problem occurs?

I'm using fontforge version 0.0.20041218-0.1; perhaps that has fixed
this bug?

   Julian



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Reply via email to