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] Wed Aug 15 13:13:43 +0000 2007 ------- TL->Regina, Laurent: Thank you for you files. They were useful. What I can conduct from further analysis and experimenting is the following: - not always will running DicOOo result in _immediate_ problems, not even if it is run in administrative mode. The problem here is somewhat more complicated and also depends on what dictionaries are already installed and who made the entries for that languages in the xcu's. - despite previously having said that always using "current user" installation only will avoid the problems, I now sadly have to confirm that even a "current user" installation _can_ result in at least a _partial_ _loss_ of linguistic functionality!! (only the share layer dictionaries will still work) There is a rather specific setup to get this kind of problem... - also you always loosing the setting with the default language has to do with mismatching entries in the xcu's. If there is a mismatch/error in a configuration that whole file will be considered as being corrupted and all it's entries get discarded. If the error was in the user layer xcu and the share layer configuration entries are all still fine the share layer configuration will be used. (Please note that the share layer configuration is actually multi-layered and there may be more than one file that modifies entries belonging to the Linguistic.xcu) If the share layer xcu is corrupted the user layer won't be read at all and the result is implementation depending. - For the very same reasons described above (mismatch/errors in the xcu files) my previously posted work-around will only do for the current session the OOo is running. After the next start it will all be the same and you one needs to apply that work-around as well. - The only 'permanent' work-around (at least until DicOOo is used again or OOo is actually upgraded!) is to shut down OOo and manually remove the linguistic.xcu's in the share layer and the user layer. Upon the next start the 'auto-detect' feature should enable all available dictionaries by deflaut. Of course changes you made manually before e.g. to the default document language need to be done again. After that the user should be fine. I will talk about the detailed problems with Linguistic.xcu, DicOO and the upgrade process with Laurent in private mails now, since I think it may start a longer thread and that need not be part of this issue. ->Regina: It would just be great if you could confirm that deleting both Linguistic.xcu's will fix your problem for the time being. So other users with the same problem can do similar. Note: Just for the books I experimented with OOo-m217 andf OOo-m225 and used DicOOo 1.7 for both. --------------------------------------------------------------------- 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]
