Apache OpenOffice (AOO) Bugzilla – Issue 76143
FreeBSD porting : I18N: Operating system doesn't support locale "en_US" at startup
Last modified: 2017-05-20 11:31:40 UTC
From FreeBSD OOo ML: http://docs.freebsd.org/cgi/mid.cgi?20070404095544.GE854 Peter Jeremy <peterjeremy@optushome.com.au> reported that: When OOo starts up, it reports I18N: Operating system doesn't support locale "en_US" After rummaging around in the OOo 2.2 code, this comes from the code in OOF680_m14/vcl/unx/source/app/i18n_im.cxx SalI18N_InputMethod::SetLocale which includes a hard-wired trial of the "en_US" locale. The correct locale name for FreeBSD should be "en_US.ISO8859-1". Is it worth adding at least a local patch to stop this warning? Could you please comment on this issue?
Reassigned to obo, since vcl/unx/source/app/i18n_im.cxx > * last change: $Author: obo $ $Date: 2006/09/17 12:32:10 $ could you please comment on this issue or reassign to the appropreate person? if it is appropreate to add something #ifdef MACOSX // MacOS X always uses UTF-8 for the filesystem osl_setThreadTextEncoding (RTL_TEXTENCODING_UTF8); locale = SetSystemLocale( "en_US.UTF-8" ); #else osl_setThreadTextEncoding (RTL_TEXTENCODING_ISO_8859_1); locale = SetSystemLocale( "en_US" ); #endif here, please reassign to me.
Hi, this code has been introduced with rev. 1.35 (CWS pj51), reassigned to obr. Oliver
IIRC, I just introduced the MacOS X specific part, the default to "en_US" was already there. @pl: would it be acceptable for Linux & Solaris to use "en_US.ISO8859-1" as well, or should we introduce a new code path for FreeBSD ?
A quick look in /usr/lib/locale on my system showed no en_US.ISO8859-1 but only en_US. So I tend to think that we do not want that on all systems; especially since most modern systems actually use UTF8 per default, not iso8859-1.
@maho: seems like adding a FREEBSD codepath is the only acceptable quick fix. Long term, the fallback locale maybe should become a configure option.
Reset assigne to the default "issues@openoffice.apache.org".