To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=69131
                 Issue #|69131
                 Summary|Glyphs with zero area cause the built in freetype to c
                        |rash
               Component|gsl
                 Version|OOo 2.0.3
                Platform|All
                     URL|
              OS/Version|Unix, X11
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|code
             Assigned to|timseves
             Reported by|timseves





------- Additional comments from [EMAIL PROTECTED] Thu Aug 31 02:23:46 -0700 
2006 -------
Some versions of freetype will crash when asked to render glyphs which have
bounding boxes of zero area.  This has been encountered with the Mondulkiri
Khmer smart font using Graphite (there is a pure OpenType version as well).
This checks for that case before atempting to render a glyph using freetype and
subsitutes an empty raw bitmap structure, thishas the added advantage of
skipping a fair amount of work that would eval to no-ops (e.g. freetype render
an invisible glyph) and that there are no zero lenght mallocs performed (zero
length mallocs still seem to return valid address so they presumably allocate a
small amount of administrative sapce from the heap anyway).

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to