i tried sending my questions to [email protected] at august
22nd, but it seems that my mail haven't even gotten to the list -
nothing in archives suggests that it did.
i was not subscribed (enough of lists for me even without that one ;) ),
but i would suspect in that case i would either receive mail informing
me that i am not allowed to post to this list, or moderator would have
either approved or rejected my message. nothing like that happened.
so i am resending my questions to discuss list. i hope that either
somebody will be able to answer them or i will be redirected to correct
list that i could post without subscribing :)
(i am subscribed to discuss)
Rich wrote:
i have some questions regarding development of dictionaries for oo.org.
i'm sorry if some of them are silly, but i have no knowledge of internal
structure of these tools and processes involving their development.
please cc me as i haven't yet subscribed to this list
1. a) would it make sense to split dictionary by functionality (for
example, base, computer terms, human names etc) ?
b) what are the benefits and drawbacks of such an approach ?
c) if a dictionary is to be split this way, does hyphenator component
also have to be split accordingly ?
2. a) what are the chances of adding a dictionary to official oo.org
distribution if it is completely developed, tested and a company has
undertaken it's supporting for several years ?
b) does it matter in such a case what language the dictionary is
(population size etc) ?
c) what steps are required, how long does such a process usually take
and how closely must developers of such a dictionary work - and with
whom - from oo.org community ?
of course, required process regarding native-lang projects should be
complied with, but i'm sure there's more to it :)
3. there must be other things that are important to achieve this goal -
there probably have been cases that we could learn from (both positive
and negative). what are major obstacles and common mistakes ? what
important principles must be considered ?
thanks
--
Rich
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
