Issue 105058 - Using icu's uchar.h when possible could simplify maintenance in gsl shaping code
Summary: Using icu's uchar.h when possible could simplify maintenance in gsl shaping code
Status: ACCEPTED
Alias: None
Product: gsl
Classification: Code
Component: code (show other issues)
Version: OOo 3.1.1
Hardware: All All
: P4 Trivial with 2 votes (vote)
Target Milestone: OOo 3.x
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-14 13:56 UTC by hdu@apache.org
Modified: 2017-05-20 11:35 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description hdu@apache.org 2009-09-14 13:56:28 UTC 
Character properties are needed for shaping. Getting them all from uchar.h can make maintenance easier 
especially when a newer unicode standard changes the character properties (e.g. unicode 4.0.0->4.0.1 
changed the bidi properties of plus and minus).
Comment 1 hdu@apache.org 2009-09-14 14:03:36 UTC 
The question of cost vs. benefit is tricky. Cost would be the risk of regressions, development, testing, 
more difficult debugging, more testing needed when using newer icu-versions.
Comment 2 Marcus 2017-05-20 11:35:12 UTC 
Reset assigne to the default "issues@openoffice.apache.org".