To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=60698
------- Additional comments from [EMAIL PROTECTED] Mon Feb 6 03:22:52 -0800
2006 -------
Hi Mathias:
> (1) User has "old" dictionary and loads it with the patched Ooo version, makes
> some changes - in which format (old or new) will the dictionary be written?
Trivial to ensure it's written in the same format - as I say; the only really
controversial piece here is that it's silently 'upgraded' to the new version:
trivial to fix.
> (2) User has a dictionary in "new" format (however he got it), but accesses
> the profile with an older, unpatched version of OOo (because e.g. he has
> two versions of OOo2 installed, but uses the same profile for both). What
> will happen?
Magic numbers will not match & he'll silently loose those user-dict words.
However - argument 2) is the same argument that is always used against almost
*any* incremental change. Sacrificing 100% forward compatibility at all times is
part and parcel of incremental feature addition; the same argument can be
deployed against adding any feature that serializes any state. This of course
has really minimal impact since a) we can make it not the default until the next
'major' release; and b) it doesn't need to 'break' existing dicts either.
> I fail to see a major user problem in this case. Yes, the file format is not
> useful for direct access by a text editor - but please explain why you think
> that it is necessary to be able to edit the user dictionary with an external
> program. That's still unclear to us.
Lock-down. I want a small perl-script to be able to edit this file; without
having to resort to strange and nasty binary bit bashing. Just such a perl
script can be found here (not perfect yet but ;-):
http://go-oo.org/ooo-build/bin/ootool.in
> There are a lot of other options to change the dictionary: use the API
> (e.g. by a Basic Macro) or change the myspell/hunspell dictionary.
A basic macro cannot be run by the super-user at package install time, or (if
you want any degree of security) at all by the super-user :-) wrt. hacking up
the system myspell/hunspell dictionary - sure; that could work - wrt. appending
strings to the global system dictionary; it's possibly even a better solution -
but the problem is that these are not managed as config files & when you upgrade
the underlying dictionary your changes will be gone.
Perhaps there is a better way of doing this with myspell dicts ? didn't look
into it; ideas appreciated.
Either way - the change is clearly an improvement over the existing twisted
binary file format :-) allows some degree of extensibility [ yes is missing a
spec. - and this is one of the rare cases where IMHO writing a spec. is
worthwhile ], and yet you don't want it :-) [ and indeed, AFAICS if it doesn't
get in in it's current state - I'm optimistic that it will never do so - it will
sit here in the issue, ignored for months, slowly gathering other requests for
enhancement & desires to extend the capabilities beyond what is
necessary/interesting for me ;-) to the point that no-one will either want to,
nor be able to implement all the suggestions & it will die a death ;-] [ I look
forward to being proved wrong on this one of course. ].
I'd love to see the feature (which incidentally re-factors some nice cut/paste
code out from IsVers20OrNewer) get in - disabled by default (fair enough) - but
at least having the capability to read 'new-format' files, and get deployed.
Then perhaps after a few minor releases your fears about co-existence with older
versions will be moot anyway [ pragmatically they will ~all support the format
].
---------------------------------------------------------------------
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]
