Hi,
The real issue here (IMHO) is that each platform/os should have a
dictionary/thesaurus/hyphenation server available that OOo, Firefox, and any
other app should use in place of installing these multiple times for each
app because each is stored in its own extension/xpi format.
Mac OSX has a dictionary server. I would bet Windows probably does as well.
It would not be that hard to convert hunspell/libhypthen/thesaurus code to
be a standalone server (localhost ports only) server project for Linux and
Solaris, and etc.
That way the dictionaries, hyphenation patterns files, synonym lists can
properly be mmapped and truly shared across multiple users and applications
with no duplication of memory usage while at the same time updated and
installed independently of any one app.
So this would solve the does not get properly updated by YOUR_APP_HERE,
while doing a complete end-run on the whole license issue since tit would
not matter if the dictionaries were full GPL, LGPL, etc since you are just
attaching to them through local sockets.
That was the original plan anyway ... I just never got there (or even
close).
My 2 cents,
Kevin
From: jonathon <[EMAIL PROTECTED]>
Reply-To: [email protected]
To: [email protected]
Subject: Re: [lingu-dev] Dictionaries in OOo 3.x
Date: Wed, 21 May 2008 08:25:50 -0700
On Wed, May 21, 2008 at 5:24 AM, Nicolas Mailhot wrote:
> The ease or goodness or whatever of creating OO.o extensions is totally
orthogonal to this problem.
+1
>This data is used by other apps and thus will be deployed by other apps
and OO.o should be able to use it directly no matter how it was deployed
without repackaging.
Especially since there are no instructions on what file to edit, and
how to edit that file, so that dictionaries don't need to be installed
as extensions.
xan
jonathon
---------------------------------------------------------------------
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]
