https://issues.apache.org/bugzilla/show_bug.cgi?id=50471
--- Comment #4 from Andreas L. Delmelle <[email protected]> 2011-01-07 07:31:03 EST --- (In reply to comment #3) > At least there should be some configuration available to the end user to tell > FOP to use some default line break in such special cases it becomes specific > to > the customer who is using FOP. Just because of some special character the > entire PDF generation should not be put in stake. Isn't it ? If given a choice > to the customer to choose from set of options, to get rid of this situation > then it is better, rather than crashing. Very right indeed. So, if no one objects, I will apply the patch as proposed. FOP will no longer crash, but simply show a '#' for such unassigned codepoints in the output. Treating them as regular alphabetic characters seems to be safe enough for the time being. Customization of and/or more refined configuration possibilities for the Unicode line-breaking algorithm is something that is still on the wish-list for the longer term. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
