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] Thu Feb  2 06:15:15 -0800 
2006 -------
Adding maccy as well to CC list.

TL->mmeeks: Thanks for providing a patch!

But I need to add some thoughts here:
- The magic header lines removed in the patch are to distinguish between
  different file format versions used for user-dictionaries since StarWriter 2.0
  Even so it is quite unlikely to still have dictionarties this old there were
  changes to the file format at least two times later on and we should still be 
  able to read those old formats.
- Also if applying a modified version of the patch right now would mean that we 
  need to take care of another new file format for those files.
  Thus it seems sth like this should better be done for a major release like
  OOo 3.0 when proper migration tools would be required anyway.
  (Migration tools are not available in minor releases)


TL->mmeeks, Lacy, maccy:

And if it is all about having the user-dictionaries more easily editable I would
suggest a completely different way to go that would have other benefits as well:

If a new file format is to be used we should use the very same file format
hunspell uses for the spellcheck dictionaries!
There are obviuosly following advantages:
- The hunspell dictionary format is easily readable and editable
- If user-dictionaries use the same format it will be easy to send those
  to the maintainer of the main dictionary to incorporate them. 
  A bonus that would be very handy!

Of course because of the UI that allows editing the user-dictionarties we would
need some API extension  that allows to modify the files.
That is we need a component (or extension to hunspell) that implements the
XDictionary and maybe XDictionaryList interface for OOo spellchecker 
dictionaries.

This probably requires to beef up the OOo dictionary format a bit beacause AFAIK
there is currently no dictionary for "Language ALL" and no support for negative
dictionaries (i.e. a list of words that should be reported as incorrect for a
defined language and allows to provide one or more suggestions).
Also it would be required to allow the user to switch on/off usage of those
dictionaries at runtime (but not for the main dictionaries that gets
pre-installed or downloaded) as it is currently possible in the UI for
user-dictionaries.

AFAIR Kevin Hendricks once mentioned that he wanted to allow "add-on's" to the
main dictionary e.g. en_US_medical, en_US_finacial, ... as positive
dictionarties and sth like en_US_bad_words as negative dictionary.
Thus the finally accepted words would be consisting from the words of the main
dictionary plus those from en_US_medical and en_US_finacial and removing all
(i.e. flagging them as incorrect) from en_US_bad_words.

If that kind of feature would be available and could be configured during
runtime by the user we can simply replace the current format of
user-dictionaries with the one the taht OOo dictionaries are using.

But I don't know how far Kevin got with this, not even if he had started with 
this.

TL->all: What do you think about the above?
Would it be possible? And is it something we like to go for?


Maybe the above idea could be extended even a little further by defining a
main dictionary for all languages and a "changes to be applied" dictionary for
the country variants.
For example:
We may have a "de" dic and aff file and de_AT, de_CH and de_DE dic and aff files
that define the changes (entries to be added/removed) to the main dictionary.
If the main dictionary is to hold only entries common to all variants then there
would also be no need for "entries to be removed" in the variant dictionaries.


Note: One other thing just came to my mind is that the current format for
user-dictionaries allows to specify hyphenation points (no alternative spellings
though). Could we have this working somehow as well?



---------------------------------------------------------------------
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]

Reply via email to