https://issues.apache.org/bugzilla/show_bug.cgi?id=49687
--- Comment #39 from Glenn Adams <gl...@skynav.com> 2011-06-22 19:29:51 UTC --- (In reply to comment #38) > The code contains a number of Unicode properties, e.g. in util.CharUtilities > and DevanagariScriptProcessor. It would be better if all Unicode properties > would be collected in one class. Perhaps it is even possible to generate that > class from the Unicode Database files. You already do that with class > BidiClassUtils. This would make it much easier to update FOP to newer versions > of Unicode. The Unicode Database files do not have the specialized properties needed to perform script the script processing found in DevanagariScriptProcessor, etc. Furthermore, there are context sensitive properties that are not simple table lookup. > Some of the info in util.CharUtilities is also provided by > Character.UnicodeBlock.of(int codePoint). Why do you not use Java's Unicode > support or ICU? Neither Java's Unicode support or ICU are sufficient to provide the necessary logic, e.g., determination of script membership for the purpose of performing complex script rendering. To give an example, script membership is not the same as unicode block membership. G. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.