To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=103399
User er changed the following:
What |Old value |New value
================================================================================
Ever confirmed| |1
--------------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
--------------------------------------------------------------------------------
Target milestone|--- |OOo Later
--------------------------------------------------------------------------------
------- Additional comments from [email protected] Wed Jul 8 14:15:23 +0000
2009 -------
So far OOo always supported some locales that were not present in ICU. This may
change over time as ICU pulls in more locales from CLDR. Anyway, OOo in its
locale data and the number formatter that uses it has more fine grained control
over number formats than ICU offers. We also have data that ICU doesn't offer at
all, so we will never completely abandon our own locale data. I also doubt we
want to replace our string classes with ICU's (we should get rid of ByteString
and UniString though and use OString and OUString instead), also because the
stable API uses OUString.
However, merging existing ICU data and OOo data during runtime where applicable
can be a long term goal, but not in the foreseeable future.
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
