Re: Tagging text as being in arbitrary complex-script languages

On Mon, 8 Apr 2019 16:17:38 +0200
Eike Rathke <erack@redhat.com> wrote:

> ScriptType value 3 here means CTL. The values are explained in
> officecfg/registry/schema/org/openoffice/VCL.xcs under
> <group oor:name="ExtraLanguage">

Thank you for the information, and thanks to Stephan Bergmann for the
localisation information.

For plodders like me, the definitions are:

officecfg/registry/schema/org/openoffice/VCL.xcs (content, as stated by
Eike)


officecfg/registry/component-schema.dtd (syntax of VCL.xcs)

officecfg/registry/component-update.dtd (syntax and some semantics of
extension writer's dictionaries.xcu; the allowed information content is
given in VCL.xcs.)

I was also able to get SIL's oxttools to work sufficiently to work out
what I needed.  A dictionaries.xcu that works is:

<?xml version="1.0" encoding="UTF-8"?>
<oor:items xmlns:oor="http://openoffice.org/2001/registry";
 xmlns:xs="http://www.w3.org/2001/XMLSchema";>
<item oor:path="/org.openoffice.VCL">
    <node oor:name="ExtraLanguages">
        <node oor:name="nod-TH" oor:op="fuse">
             <prop oor:name="Name" oor:type="xs:string">
                 <value>Northern Thai</value>
             </prop>
             <prop oor:name="ScriptType" oor:type="xs:int">
                 <value>3</value>
             </prop>
        </node>
    </node>
</item>
<item oor:path="/org.openoffice.Office.Linguistic">
 <node oor:name="ServiceManager">
    <node oor:name="Dictionaries">
        <node oor:name="HunSpellDic_nod-TH" oor:op="fuse">
            <prop oor:name="Locations" oor:type="oor:string-list">
                <value>%origin%/nod_TH.aff %origin%/nod_TH.dic</value>
            </prop>
            <prop oor:name="Format" oor:type="xs:string">
                <value>DICT_SPELL</value>
            </prop>
            <prop oor:name="Locales" oor:type="oor:string-list">
                <value>nod-TH</value>
            </prop>
        </node>
    </node>
 </node>
</item>

The LibreOffice extension manager seems tolerant and has some helpful
error reporting.  *My* next step is to sort out copyright issues so
that I can share the dictionary.

Richard.