Apache OpenOffice (AOO) Bugzilla – Issue 61465
Thai installation set should be bilingual by default - with Thai and en_US UI
Last modified: 2007-02-06 12:11:48 UTC
Translation for OOo has been done for Thai in 2.0.1. Even though many Thai will like the Thai UI, many will be confused and prefer the English UI. Therefore the Thai installer must include both Thai and en_US UI. Currently, the build process is producing only Thai installation set. It should be changed to include both Thai and en_US.
@ is: Something for you?
Just adding th to the following list? bin/modules/installer/globals.pm: @noMSLocaleLangs = ( "dz", "km", "nr", "ns", "rw", "ss", "st", "ts", "tn", "ve", "xh", "zu" , "ne" , "bn", "bn-BD", "bn-IN", "lo", "cy" );
I do not like the solution to use @noMSLocaleLangs. This forces the creation of bilingual installation sets. But this is not necessary for Thai, because the Windows Installer works fine with Thai. If you want bilingual installation sets, just create them in instsetoo_native (dmake openoffice_en-US_th), but we do not need to force this. Therefore I think, there is nothing to do.
is: I agree with you. If it works in Windows even without en-US, it should not be forced. And you can use dmake openoffice_en-US_th is: I think we can fix it with WONTFIX because the processes and makefiles inside OOo doesn't prevent to generate dual language instsets.
This issue comes from pjanik's comment in issue 60034 ------- Additional comments from pjanik Wed Feb 1 00:57:56 -0800 2006 ------- samphan, james_clark: is Thai to be built as dual installer by default? Right now, the build process is producing only Thai installation set, not en-US_th... If so, please file new issue. ------- So I actually want the (esp. Sun generated) Thai installer to be bilingual by default.
Clearly it should not be forced: people should be able to generate both Thai only or multilingual Thai/en_US installation sets. However, there ought to be some documented value that can be included in the --with-lang option to configure, such that a top-level dmake will generate a multilingual Thai/en_US installation set. It shouldn't be necessary to run a separate dmake in a subdirectory with an obscure argument in order to get the normal installation set for a Thai environment.
Ause, do you think you can introduce such a "bilingual" setting?
ause: Hmm, maybe something like configure --additional-instsets="en-US_th cs_sk" -> ADDITIONAL_INSTSETS="en-US_th cs_sk" and dmake openoffice_en-US_th openoffice_cs_sk in instsetoo_native/util could be really interesting!
*** Issue 64989 has been marked as a duplicate of this issue. ***
i don't see much benefit replaceing the "obscure dmake parameter" with yet another configure parameter. if configure passes something like ADDITIONAL_INSTSETS="en-US_th cs_sk", it's of cause possible to let this do some additional packaging in "instsetoo_native/util". who is able to provide the configure chamnges?
rene? What do you think about it? Is it worth the effort at all?
anyone stil interested in this issue?
closing due lack of interest...
.
finally closed...