https://bugs.documentfoundation.org/show_bug.cgi?id=143853

            Bug ID: 143853
           Summary: RegistryModifications setting for Asian language
                    cannot be simply set false
           Product: LibreOffice
           Version: Inherited From OOo
          Hardware: All
               URL: https://wiki.documentfoundation.org/Development/Extens
                    ion_Development
                OS: All
            Status: UNCONFIRMED
          Severity: trivial
          Priority: low
         Component: framework
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected]

This may not be a bug but it should be documented here. 
I was inspired by what Justin wrote in bug 143578 and read this URL and took
his sample OXT configuration extension and was able to extend it.
I added Expert configuration, Macro, Outline and it all worked with the
extension (to be added via unopkg).

I also tried to remove Asian language and Complex text layout but it only half
worked. 

I couldn't remove Asian language in common.xcu with:
<node oor:name="I18N">
 <node oor:name="CJK">
   <prop oor:name="AsianTypography" oor:type="xs:boolean" oor:finalized="false"
>
    <value>false</value>
   </prop>
 </node>
</node> 

Contrary to Asian, CTL removal seems to work when set in the same I18N node
with:
<node oor:name="CTL">
 <prop oor:name="CTLFont" oor:type="xs:boolean" oor:finalized="false" >
   <value>false</value>
 </prop>
</node>

I checked xmldiff from new RegistryModifications.xcu and one after I manually
turned off Asian and CTL.

It has:
<item>
  <prop oor:name="AsianTypography" oor:op="fuse"/>
</item>

Where is "false"? What is "fuse"?

It also added many CJK and CTL related settings whose default value is "false"
or "0" anyway, or is "true" for Ignore property. 

So, question or bug is: why I coudn't set false to AsianTypography via this
modification and turn off Asian language support?

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to