To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=72559
------- Additional comments from [EMAIL PROTECTED] Tue Aug 14 13:19:03 +0000 2007 ------- tl->laurent: I'm not yet done with my investigation but I can confirm that just by running you macro below with isAdmin set after the next Office start nothing will work anymore. (I don't need to install dictionaries to have this effect). I'm a bit puzzled because adding sth to the share layer xcu should not have this effect (unless the user layer xcu has still meaningful content). This even happens even though the settings in Tools/Options/.../Writing Aids say everything is fine and available! But there is also an easy work-around for the problem. On the "Writing Aids" page itself where the three check boxes for spell checker, hyphenator and thesaurus are you just need to do the following: - unceheck each of the 3 entries then check all of them again and leave the dialog via the 'OK' button. Right after this everything will be fine again. ->Laurent: Actually two problems met here in this issue: a) as MBA described installing in the share layer is a problem in itself (at least for later add-ons that were not part of the original installation) b) the change to the xcu in the share layer should not have had this effect If I have to make a quick but maybe wrong guess about the problem with the entries you make in the share layer xcu it will be this: - In the user layer xcu all the Spellchecker, Hyphenator, LastSpellchecker, .... list are using oor:type="oor:string-list" for their entries. Which maches the setup in the xcs file. - the entries you make use oor:type="xs:string" which is a type mismatch and will probably trigger an exceptin when the user xcu is read. Because of this we will also likely have a Linguistic.xcu.bak in the user layer which usually remains when an exception was encountered. Also you need not all make entries in the linguistic xcu in order to have new installed dictionaries functional. You leave everything to OOo. The DataFilesChangedCheckValue was originally setup to check the pathes share/dict and share/dict/ooo for any changes and activate new installed dictionaries and everything was fine. Then you and I had a communication failure: I was not aware that because of another issue you need to install downloaded dictionary now to user/wordbook (which was not included in the calculation for DataFilesChangedCheckValue). Thus you needed a change in the user layer xcu to make those dictionaries work. If you had told me about this new installation path I could have just extenden the evaluation of DataFilesChangedCheckValue to that path as well. Actually sometime after I found out that there is a new installation path (which was probably already several month after it was used first) I extend the pathes to look in by user/wordbook. That missed to tell you as well... -_-° The bottom line is: since some time ago in current Office versions you need no longer make changes to the xcu in order to have your downloadable dictionaries functional by default. The 'auto-detect' feature will take care of it in user/wordbook as well. Your task could be scaled down to just keep the dictionary.lst in shape. Finally just let me remind you again that the statement a) from MBA is still valid! Thus the only good work around to prevent the problem for the time being is to not use administrative installation! And in the longer run we should go with extensions. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
