Apache OpenOffice (AOO) Bugzilla – Issue 21191
non-unixy i18n setup ...
Last modified: 2005-01-10 14:47:44 UTC
As we all know - in order to get i18n to work sensibly on multi-user unix systems, you have to start fooling around with XML files in the user's config to try and sych OO.o's idea of locale with the systems's idea. This patch fixes this - it also expands the RTL API to allow (at least) 2 types of system locale to be queried: Messages vs. Ctype - of course, we should support numeric etc. as well to be good citizens - but this is a start. Of course - due to the way the architecture for getting this sort of thing is designed, this is a large, painful, ugly, distributed, UNX conditional patch. Input on how to proceed very much appreciated.
Created attachment 10315 [details] changes to sal/osl
Created attachment 10316 [details] lots of scattered hacks.
TM->MH: Please have a look, thanks !
mh->hro: can you please review and repatch to appr. developers
Reassigned.
Accepted.
set issue type to PATCH.
As agreed by nearly all (sun) developers involved in i18n on dev@framework a couple of weeks ago, the proposed patch is not the preferred way to solve the problem - and it is missing the Windows implementation of the SAL part. However we are pretty close to provide platform specific values transparently through the OOo configuration API, so I am adding this task to the planned CWS syssettings01.
no one should contest that the patch is ugly; cf. the first comment: > Of course - due to the way the architecture for getting this sort of thing is > designed, this is a large, painful, ugly, distributed, UNX conditional patch. A more beautiful design was not forthcoming on the list when I enquired in Oct 2003 though, so what can one do.
Hi Michael, I was asked via email to state in the issue why I had not applied your patch up to now. I didn't want to disqualify the research you have done to make OOo work as expected on Unix. I appologize if you got this impression. I thought there was an agreement in this discussion that the functionality should hooked into the OOo configuration transparently. We now have the necessary infrastructure at place to do so; sample code for this (connecting to gconf) is already available in gsl/shell. Maybe we should wait a little bit longer because JB is going to change the key containing all installed languages. I'am going to ask him when this will happen. However: it's a good thing to have your patch at hand which touches all impacted code peaces and I would by glad if your time would allow to help out once more to fix this issue !
Implemented as specified in CWS syssettings01.
obr @ of: please verify.
of: Verified in cws syssettings01
of: Looks good in src680m71