To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=111019 Issue #|111019 Summary|sal: since rtl_Locale was written, three letter langua |ge codes were introduced in glibc Component|porting Version|DEV300m76 Platform|All URL| OS/Version|Linux Status|NEW Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P3 Subcomponent|code Assigned to|sb Reported by|cmc
------- Additional comments from c...@openoffice.org Tue Apr 20 14:35:27 +0000 2010 ------- But the parser in osl/unx/nlsupport.c assumes two letter codes. e.g. if( pLocale && pLocale->Language && (pLocale->Language->length == 2) ) etc. some real locales in my glibc-2.11.90 export lang=nan_tw.ut...@latin or export LANG=hsb_DE.UTF-8 give results like... Language is "na" Country is "" Variant is "n_tw.ut...@latin" from sal's Locale code. In general I guess no-one notices because a) The various bits of the string get stuck back together again before any meaningful use of them is made b) The fields of rtl_Locale rarely get used elsewhere --------------------------------------------------------------------- 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...@porting.openoffice.org For additional commands, e-mail: issues-h...@porting.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
