Re: OOo 2.0's osxlocale.c
Etsushi Kato <[email protected]>
| Newsgroups | gmane.comp.openoffice.devel.porting |
|---|---|
| Message-ID | <[email protected]> |
On Fri, Apr 08, 2005 at 06:06:54PM +0200, Eric Hoch <[email protected]> wrote: > > With the test program, it returns following result. > > > > Czech -> cs_CZ > > Romania -> ro_RO > > Chinese -> zh_CN > > Chinese (Taiwan) -> zh_TW > > > > This seems to be valid locale name for me. > > I only get > > German de_DE > > as output. You need to change 'System Preferences' -> 'International' -> 'Formats' -> 'Region' to test this. > >> So we need some more "exotic" languages to test this patch with and > >> look if it does their encoding right. I think I can ask one arabian > >> speaking person if he can test one OOo with this patch and see if > >> arabian names are displayed correctly. > > > > Maybe the test program can help for these languages. > > Hope so. With some test, Algeria (Arabic) -> ar_DZ Oman (Arabic) -> ar_OM Also from Apple's "Working With Locales" ([1]) and "Locale Concepts" ([2]) documents, CFLocaleCopyCurrent() is supposed to produce valid locale name (lang and region). GNU gettext is now using same mechanism (CFLocaleCopyCurrent) of getting locale name. The real problem is that OS X libc's locale is not complete; it lacks these Arabic locales; setlocale(3) always fails for them (see /usr/share/locale/). I think this is another story. [1] http://developer.apple.com/documentation/CoreFoundation/Conceptual/CFLocales/Articles/CFLocaleWorking.html [2] http://developer.apple.com/documentation/CoreFoundation/Conceptual/CFLocales/Articles/CFLocaleConcepts.html -- Etsushi Kato [email protected]