Hi,

Joerg Barfurth wrote:

Ingo Schmidt wrote:

Do you want, that khmer is the preselected value and not the currently used value "default"? This is a change in the configuration.

-> Joerg, do you know how to change the default value for the configuration?


Yes. If you just want to do that for your build, with a patch, you can add that setting to officecfg/registry/data/org/openoffice/Office/Linguistic.xcu



Apparently there is no such file now, so you could simply add one for your build. I have attached an example. In case the attachment does not come through, here is the content:


<?xml version="1.0" encoding="UTF-8"?>
<oor:component-data xmlns:oor="http://openoffice.org/2001/registry";
                    xmlns:xs="http://www.w3.org/2001/XMLSchema";
                    oor:name="Linguistic"
                    oor:package="org.openoffice.Office">
 <node oor:name="General">
  <prop oor:name="UILocale" oor:type="xs:string">
   <value>km-KH</value>
  </prop>
  <prop oor:name="DefaultLocale_CTL" oor:type="xs:string">
   <value>km-KH</value>
  </prop>
 </node>
</oor:component-data>

You have to get this file installed to $officeprefix/share/registry/data/org/openoffice/Office/.

For this purpose, you need to (a) get it built and delivered to solver during your build and (b) get the file packed by the installer.

For (a), put the file into directory $SRC_ROOT/officecfg/registry/data/org/openoffice/Office/ and add it to the makefile.mk there.

For (b), add an entry for the file in scp, e.g. in file $SRC_ROOT/scp2/source/ooo/file_ooo.scp. Take an existing entry for a neighboring xcu file (e.g. Views.xcu) as an example. Be sure that the entry gets a unique gid_... identifier.

You also need to enable CTL for khmer. For this purpose you have to add khmer (i.e. km-KH) to the languages for which file Common-ctl.xcu is installed. This also is in file_ooo.scp, under entry gid_File_Registry_Spool_Oo_Common_Ctl_Xcu. This modification should actually be committed to the OOo repository.

Disclaimer: I have never tried preselecting a (CTL) language this way. If you find that this does not set all the settings you want, feel free to ask again.

OTOH if you want to integrate that into the common office tree, things get more difficult and there are some semantic difficulties.


The problem with preselecting a language this way, is that the language-selection setting is (has to be) stored in the language-independent part of the configuration. Thus if you add these (Linguistic.xcu) settings, even if you restrict them to be installed only for khmer, then in any multi-lingual installation that has khmer installed (possibly as one of 25 languages) the preselection will be khmer. And if other languages want a similar preselection, then there is conflict that can't be solved.


Because of this, such a preselection should only be done in your private build that is created explicitly for a khmer audience, but can't be integrated into the OOo codebase proper. (You could make that a separately installable package, but that is more complicated than the solution I described).

OTOH the modification to enable CTL when kmher is UI language by installing Common-ctl.xcu can and should be integrated back.

Ciao, Joerg

--
Joerg Barfurth              Sun Microsystems - Desktop - Hamburg
>>>>>>>>>>>>>>>>>> using std::disclaimer <<<<<<<<<<<<<<<<<<<<<<<
Software Engineer                         [EMAIL PROTECTED]
OpenOffice.org Configuration          http://util.openoffice.org


<?xml version="1.0" encoding="UTF-8"?>
<oor:component-data xmlns:oor="http://openoffice.org/2001/registry"; xmlns:xs="http://www.w3.org/2001/XMLSchema"; oor:name="Linguistic" oor:package="org.openoffice.Office">
 <node oor:name="General">
  <prop oor:name="UILocale" oor:type="xs:string">
   <value>km-KH</value>
  </prop>
  <prop oor:name="DefaultLocale_CTL" oor:type="xs:string">
   <value>km-KH</value>
  </prop>
 </node>
</oor:component-data>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to