Bug 41999 - [PATCH] Unassigned code points cause ArrayIndexOutOfBoundsException in LineBreakUtils
Summary: [PATCH] Unassigned code points cause ArrayIndexOutOfBoundsException in LineBr...
Status: RESOLVED FIXED
Alias: None
Product: Fop - Now in Jira
Classification: Unclassified
Component: general (show other bugs)
Version: all
Hardware: Other other
: P2 normal
Target Milestone: ---
Assignee: fop-dev
URL:
Keywords:
Depends on: 50471
Blocks:
  Show dependency tree
 
Reported: 2007-03-30 11:50 UTC by Keith Stribley
Modified: 2012-04-20 23:33 UTC (History)
2 users (show)


Attachments
unassigned-linebreak-property.patch (834 bytes, patch)
2007-03-30 11:54 UTC, Keith Stribley 		Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Keith Stribley 2007-03-30 11:50:46 UTC 
Documents that contain proposed new code points to unicode, such as those listed
at http://www.unicode.org/alloc/Pipeline.html have a LineBreakProperty of zero
as returned by LineBreakUtils.getLineBreakProperty(c). This then causes an index
out of bounds exception in LineBreakUtils.getLineBreakPairProperty() when built
from trunk.

One solution might be to use LineBreakUtils.LINE_BREAK_PROPERTY_XX instead of
zero for unassigned code points.
Comment 1 Keith Stribley 2007-03-30 11:54:48 UTC 
Created attachment 19851 [details]
unassigned-linebreak-property.patch

a patch that uses LineBreakUtils.LINE_BREAK_PROPERTY_XX when the line break
property class is zero to avoid the index out of bounds exception.
Comment 2 Glenn Adams 2012-04-07 01:43:00 UTC 
resetting P2 open bugs to P3 pending further review
Comment 3 Glenn Adams 2012-04-11 03:22:17 UTC 
increase priority for bugs with a patch
Comment 4 Dominik Stadler 2012-04-19 08:24:46 UTC 
Isn't this already fixed by Bug 50471
Comment 5 Glenn Adams 2012-04-20 23:33:50 UTC 
Fixed by Bug 50471