Hi Javier,
Ingo,
Thanks, just a couple of small questions more.
So, this is the problem that we have for languages like Khmer, that are not supported by Windows, the loader chooses Khmer automatically and then it does not work because Windows does not accept it.
I guess we could have a patch somewhere in private builds in which the loader was forced to use English in the Installation, so that we do not need to always create bi-lingual installers. Would this be possible? If so, in which file?
hmm, this is not my project, but of course it should be possible. I will look for this.
setup_native/source/win32/msi-encodinglist.txt <http://installation.openoffice.org/source/browse/installation/setup_native/source/win32/msi-encodinglist.txt> You need a line of the type
km 0 1107 # Khmer
> Correct
ummm.... Pavel has mentioned that there is a problem with this when he tried to build it. Issue 47857, because of the 0 value.
Yes, there seems to be a problem. I will have to investigate this.
---------------------
In file scp2/source/ooo/file_ooo.scp
<http://installation.openoffice.org/source/browse/installation/scp2/source/ooo/file_ooo.scp>
file you need to make sure that - *if your language is a CTL language* - the file Common-ctl.xcu is installed, and *if it* is *a CJK language*, Common-cjk.xcu and Writer-cjk.xcu get installed. Look for these file names within file_ooo.scp and a a new line for your language. As an example, for Khmer (km) - a CTL language - you should add the line in bold below:
File gid_File_Registry_Spool_Oo_Common_Ctl_Xcu
TXT_FILE_BODY;
Styles = (PACKED,MAKE_LANG_SPECIFIC);
Dir = gid_Dir_Share_Registry_Modules_Oo_Office_Common;
Name (th) = "/registry/spool/org/openoffice/Office/Common-ctl.xcu";
Name (hi-IN) = "/registry/spool/org/openoffice/Office/Common-ctl.xcu";
Name (ar) = "/registry/spool/org/openoffice/Office/Common-ctl.xcu";
Name (he) = "/registry/spool/org/openoffice/Office/Common-ctl.xcu";
* Name (km) = "/registry/spool/org/openoffice/Office/Common-ctl.xcu";*
End
Correct, please take care of the new flag "MAKE_LANG_SPECIFIC" that renames this file in packing process, to make the filename language specific. This was necessary to avoid conflicts in language packs and multilingual installation sets.
By 'take care' you mean that it is correct the way it is, with the "MAKE_LANG_SPECIFIC" flag as it is in the example? Or a change somewhere else is required?
No further change is required, I just wanted to explain the meaning of the new flag.
Greetings
Ingo
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
