Hi Thomas, Hi all
Thomas, first thanks for launching this topic. some rough thoughts
- share/dict
the path where implementation specific dictionaries for spell checker,
hyphenator and thesaurus go, as well as OOo linguistic specific
sub-directory "ooo"
i always saw share/dict/ooo
not share/dict
that is here where DicOOo puts files when used in administartive mode
- share/wordbook
where user-dictionaries that get pre-installed and are not
user-editable go,
soffice.dic sun.dic
btw, i think that all dictionary files should be plain text-files
- user/wordbook
where user-dictionaries (the ones that can be modified via the UI) go,
namely those that a user can create, and (due to lack of a better
choice at that time) also the place where currently downloadable OOo
dictionaries get installed to.
yes.
- and soon share/fingerprint
the files needed for language guessing
ok.
why not gathering all linguistic ressources inside a directory ?
share/dict ? or share/linguistic ?
(share dict would be backward compatible)
share/linguistic/ooo
share/linguistic/wordbook
share/linguistic/fingerprint
One goal would be to use a multi-path for user/wordbook and
share/wordbook. Another would be to resolve the conflict of
user-dictionaries and downloadable dictionaries in user/wordbook,
especially since both of them happen to use the same file extension. :-/
I never heard conflict names for 3 years
why do we need multiple path ? to share dictionaries between
applications ? Is it planned for the 3 types (DICT, THES, HYPH)
The more general goal would be to make the path settings more flexible
and extensible. (For example as it is already the case for templates.)
And especially we would like to be able to deploy
additional/downloadable dictionaries in the future as packages.
Is this why we need flexible path settings ?
do we really need to open (via user interface) the wordbook paths
modification ? can lead to misconfigurations from end-user ?
So if anyone is interested to discuss this topic just drop a note here
in the ML. We will see later on if we should discuss this here or via IRC.
So, here i am :)
I just put some rough reflexions and may be totally wrong on some
topics, but this is for starting the discussion
Laurent
--
Laurent Godard <[EMAIL PROTECTED]> - Ingénierie OpenOffice.org -
http://www.indesko.com
Nuxeo Enterprise Content Management >> http://www.nuxeo.com -
http://www.nuxeo.org
Livre "Programmation OpenOffice.org", Eyrolles 2004-2006
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]