Apache OpenOffice (AOO) Bugzilla – Issue 15362
Linguistic: configuration item broken by incorrect setup entries
Last modified: 2013-02-24 20:34:28 UTC
When you look in share\registry\data\org\openoffice\Office\Linguistic.xcu the entries for the Hyphenator list look like: <node oor:name="HyphenatorList"> <prop oor:name="da-DK" oor:op="replace" oor:type="oor:string-list"> <value>org.openoffice.lingu.LibHnjHyphenator</value> </prop> The type has to be oor:type="xs:string" for the HyphenatorList and for the HyphenatorList only (the lists for the spell checker and thesaurus are correct!) The mismatch causes a parsing error in the configuration and in the final consequence an invalid configuration item. Thus all property values on that item are often incorrect and won't get saved or loaded correctly.
Target set to OOo 1.1 RC.
Hi Thomas, Thanks! Luckily all of those style entries have just gone away with yesterday's commits to cws_srx644_ooo11beta2. Since you nicely changed OOo 1.1 to auto register any dictionaries supported by getLocale(), I no longer have to register individual hyphenation dictionaries. So the current scp/source/lingu/files_lingu.scp is quite simple, it registers 3 components (one for thesaurus, hypehnation, and spellchecking) but delivers whatever dictionary pieces as a simple zip and then lets your call to getLocale() to register the individual dictionaries. So I think we can resolve this one as fixed in cws_srx644_ooo11beta2 tree as of yesterday. Thanks, Kevin #include "szipmac.inc" #include "gid.inc" // ******************************************************************* // Directories Directory GID_DIR_SHARE_DICT ParentID = GID_DIR_SHARE; DosName = "dict"; Styles = (CREATE); End Directory GID_DIR_SHARE_DICT_OOO ParentID = GID_DIR_SHARE_DICT; DosName = "ooo"; Styles = (CREATE); End // Files File GID_FILE_LIB_ULINGU TXT_FILE_BODY; Styles = (PACKED); Name = LIBNAME(ulingu); Dir = GCFG_BINARY_DIR; End File GID_FILE_LIB_LTH TXT_FILE_BODY; Styles = (PACKED,UNO_COMPONENT); RegistryID = GID_STARREGISTRY_SERVICES_RDB; Name = LIBNAME(lth); Dir = GCFG_BINARY_DIR; End File GID_FILE_LIB_SPELL TXT_FILE_BODY; Styles = (PACKED,UNO_COMPONENT); RegistryID = GID_STARREGISTRY_SERVICES_RDB; Name = LIBNAME(spell); Dir = GCFG_BINARY_DIR; End File GID_FILE_LIB_HYPH TXT_FILE_BODY; Styles = (PACKED,UNO_COMPONENT); RegistryID = GID_STARREGISTRY_SERVICES_RDB; Name = LIBNAME(hyphen); Dir = GCFG_BINARY_DIR; End File GID_FILE_ZIP_WRITINGAIDS TXT_FILE_BODY; Styles = (ARCHIVE); Dir = GID_DIR_SHARE_DICT_OOO; Name = "writingaids.zip"; End
*** Issue 15361 has been marked as a duplicate of this issue. ***
*** Issue 15885 has been marked as a duplicate of this issue. ***
*** Issue 15876 has been marked as a duplicate of this issue. ***
*** Issue 15494 has been marked as a duplicate of this issue. ***
*** Issue 15937 has been marked as a duplicate of this issue. ***
*** Issue 16030 has been marked as a duplicate of this issue. ***
*** Issue 15194 has been marked as a duplicate of this issue. ***
*** Issue 14916 has been marked as a duplicate of this issue. ***
*** Issue 13793 has been marked as a duplicate of this issue. ***
In Oo0 1.1.0 (but after upgrading from Ooo1.1Beta2) I still had to edit and correct the Linguistic.xcu file to be able to make my Default Language for Documents permament. See also Issue 19363.
Hi, Yes, that is to be expected. Once a .xcu gets broken, all upgrades will carry along that user's broken Linguisitic.xcu. That is why I (personally) would not do an "upgrade" install from any development or beta release to a stable release. In fact, given the speed of change of OOo, I would not recommend an upgrade install at all unless it was specifically a minor dot release change of a stable series (1.1.0 to 1.1.1). Thanks, Kevin
verfied in 1.1.0.
close issue