To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=72559
User mba changed the following:
What |Old value |New value
================================================================================
CC|'cornouws,jolatt,laurentgo|'cornouws,jolatt,laurentgo
|dard,mba,thing' |dard,mba,thing,tl'
--------------------------------------------------------------------------------
IssuesThisDependsOn| |80286,80287
--------------------------------------------------------------------------------
Target milestone|--- |OOo 2.x
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Mon Aug 13 14:18:03 +0000
2007 -------
Please let me try to de-emotionalize the discussion and get back to the facts.
If dictionaries are installed per user all files and the necessary information
about them are stored in the "user" layer of OOo. In this case an update of OOo
shouldn't delete any dictionaries or dictionary configurations. (In case I'm
wrong here please let me know.)
So the only way how OOo can destroy dictionaries or dictionary configurations is
when dictionaries have been put into the "share" layer. This will happen in two
cases:
(1) Manual installation of dictionaries
(2) "Administrative setup" of DictOOo (the dictionary wizard of OOo)
(The "Current User Setup" of DictOOo is no problem as the dictionary and
dictionary configuration files are placed into the "user" layer and the
situation is as described above.)
I would be pleased to hear which scenario was used by the users who have been
hit by the problem or if other scenarios have been used that I'm not aware of.
While scenario (1) is unsupported and discouraged case (2) is the problem.
Whatever we do in the OOo source code to fix the problem it will fail as long as
the "Administrative setup" of DictOOo is carried out in the way it is
implemented now. We need a new implementation for this mode: administrative
installation of dictionaries must use dictionary extension packages and *never*
change any files in or add any new files to the "share" layer. To make it simple
dictionaries should be installed as extensions always, in both modes.
Work has been done to prepare the OOo source code to deal with dictionaries
installed as extensions (see Child Workspace tl41 - I made this issue dependent
to the issues added to the CWS). We think that this code can be ready and tested
for OOo 2.4.
Now we need to create extensions from all existing dictionaries. We (the OOo
developers) can do this for all dictionaries that are hosted in our cvs but we
need to get in touch with all other contributors that currently host
dictionaries on their own websites. We will start a discussion about that on the
lingucomponent mailing list soon.
Until then there is a simple though perhaps sometimes painful workaround: don't
use the "Administrative Setup" of DictOOo.
The target "2.x" should reflect that we still need the commitment of the
external contributors to fix the problem completely. We hope to deliver a fix
for the most common dictionaries (those we can manage ourselves) in 2.4.
---------------------------------------------------------------------
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]
