To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=103399





------- Additional comments from e...@openoffice.org Fri Aug 21 13:31:12 +0000 
2009 -------
Please note that patterns may contain calendar and native numbering information,
also mixed representations within one pattern are possible, eras, and some
specific handling that arose of the need to mimic Excel display formatting
behavior when using such patterns. I strongly doubt ICU handles all that. For
reference you may take a look at the number formatter implementation in
svtools/source/numbers/, specifically zformat.cxx 
SvNumberformat::ImpGetDateOutput(), SvNumberformat::ImpGetTimeOutput() and
SvNumberformat::ImpGetDateTimeOutput(). I also don't see the need why we should
replace the current formatting with ICU; instead, we should obtain the necessary
data from ICU where possible.

We then could add some features such as possessive month names, possibly call
ICU where the OOo i18n framework doesn't have a solution yet, and replace the
duplicated i18npool calendar implementations with the ICU calendar.

However, I think obtaining locale data such as day and month names and their
abbreviations from ICU and merge it into OOo locale data layer if not defined in
OOo locale data should be one of the first steps, so we can get rid of
duplicated data definitions in OOo.

In this context you may be interested in two older surveys we did, comparing OOo
and CLDR locale data. The data probably is outdated, but there are some comments
why we kept OOo specific locale data in favor over CLDR locale data in some 
cases.

http://l10n.openoffice.org/nonav/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html
from 2005

http://l10n.openoffice.org/nonav/i18n_framework/cldr/LocaleDataAudit_OOo202.html
from 2006


---------------------------------------------------------------------
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: issues-unsubscr...@l10n.openoffice.org
For additional commands, e-mail: issues-h...@l10n.openoffice.org


---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org

Reply via email to