Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=600108

--- Comment #6 from Paul Flo Williams <[email protected]> 2010-07-26 07:41:07 
EDT ---
To track down the glyph, I just changed FVStrokeItScript() to print the glyph
name being processed at the time of the crash.

Since then, I've been tracking the changes in CVS and running serafettin's
scripts against the font each time.

I hadn't tried to identify any other crashing glyphs because I was hoping that
a fix for that one, when it's found, would apply to all. I haven't investigated
why the new spline-stroking algorithm is failing because the overlap code is in
flux in CVS and I'm hoping George will fix it before I hunt it down!

I can produce a list of the other bad glyphs if you like, but it won't be until
tomorrow evening. (Feel free to email me for progress.) Or, I could start
trying to fix the crash.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
_______________________________________________
fonts-bugs mailing list
[email protected]
https://admin.fedoraproject.org/mailman/listinfo/fonts-bugs
http://fonts.fedoraproject.org/

Reply via email to