You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some fonts have name table entries where the name bytes field is empty (zero
length), and additionally has the index to the entry equal to the bounds of the
name table.
Extra bounds checking introduced with r155 causes sfntly to crash on such
entries with an IndexOutOfBounds exception. I believe that in this case, such
entries are valid (since the length is zero) and sfntly should not throw an
exception.
Original issue reported on code.google.com by [email protected] on 10 Jul 2013 at 4:22
Original issue reported on code.google.com by
[email protected]
on 10 Jul 2013 at 4:22Attachments:
The text was updated successfully, but these errors were encountered: