On Mon, Nov 07, 2011 at 06:00:49PM -0800, Pedro Giffuni wrote:
> > > On the long run I think the Apache-Way means we give
> > > prevalence to freedom over features so we either move
> > > back to MySpell 
> > 
> > it has already been said that MySpell is a step backward
> > 
> 
> It is, but can't we have both MySpell and HunSpell? It is
> good to have alternatives.

the good thing about this is that in OOo these tools are UNO components,
so anyone in the know can develop a set of linguistic UNO components
that use MySpell and its dictionaries without needing to modify a single
line of code, nor compile  OOo by themselves.
IIRC Duden, the German company, provided support for OOo in this way.


> > Look at the folders:
> > http://svn.apache.org/viewvc/incubator/ooo/trunk/main/hunspell/
> > http://svn.apache.org/viewvc/incubator/ooo/trunk/main/mythes/
> > http://svn.apache.org/viewvc/incubator/ooo/trunk/main/hyphen/
> > 
> > there are only patches and makefiles, no copyleft source.
> > AOOo can keep Hunspell based linguistic components, there
> > is no need to remove anything, it is already IP-clean.
> 
> I know, I know.. but why download tarballs when you can use:
> 
> --with-system-hunspell
> --with-system-mythes

you can not use this for Windows, and is discouraged for a generic Linux
build.

> (Which is also used by LibreOffice AFAICT)

I doubt they use system hunspell/mythes/hyphen for Windows or generic
Linux builds.

> > The situation is almost the same as before.
> > 
> 
> The only issue is the Italian dictionary, which is GPL-only
> and we can't include at all.
> 
> Now let's be realistic: we don't develop dictionaries here
> in AOOo (that I know of) and due to license issues our
> repositories and source distributions can't carry them
> anyway. Why not build all of them in apache-Extras or
> wherever and link them there for users?

dictionaries are extensions. They have their place at
http://extensions.services.openoffice.org/en/dictionaries
The people actually developing the dictionary build the extension and
upload them to that site.
The same situation as before (the only issue is with the extension's
site not working properly).

Of course, this could be made more user-friendly, prompting the user, on
application first run, if she or he wants to install a dictionary
extension for his language, etc.

Regards
-- 
Ariel Constenla-Haile
La Plata, Argentina

Attachment: pgp44CrDIXDvl.pgp
Description: PGP signature

Reply via email to