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





------- Additional comments from [email protected] Fri Jul  3 22:40:25 +0000 
2009 -------
We already have so-SO locale data, which was added with issue 83369.
Your data actually differs quite a bit, I'll attach a diff, please review and
give me a go/no-go on your changes, or better, attach a corrected diff.

At least your change to the currency is not correct, because the ISO 4217 code
for the Somali Shilling is indeed SOS and not SSH.
http://en.wikipedia.org/wiki/Somali_shilling also lists "So. Sh." as the
currency symbol and not "$$H".

The changes to DateSeparator and ThousandSeparator appear to be correct,
compared with the ICU http://demo.icu-project.org/icu-bin/locexp?d_=en&_=so_SO
and the CLDR http://www.unicode.org/cldr/data/charts/by_type/number.pattern.html
data charts.

Changes to currency format codes also seem to be correct, but I have doubts
about the percent formats, the blank between amount and % percent sign doesn't
appear in ICU or CLDR charts.

Your DefaultAbbrvName for Thursday, Kham, has 4 instead of 3 letters, which I
don't find in ICU or CLDR.  Also several abbreviated month names have 4 letters.
I don't say these are wrong, just that I don't find them in neither the ICU nor
CLDR charts, they list 3 letter abbreviations. The abbreviation for February
changes from "Feb" to "feb", which looks like an error.

Please review in detail.
Thanks
  Eike


---------------------------------------------------------------------
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]

Reply via email to