I am very interested in Apertium, especially if it is possible to grow it for biblical Greek and Hebrew.

Licensing threads seem to generate more heat than light. I hope that my question won't. I develop code under many different licenses including GPL, and feel that following licenses properly is important.

With Apertium being GPL, not LGPL, the license is "viral".

I have a non GPL library in which I'd like to use the code. Will the code in contrib protect my code from the viral nature of the GPL?

About the only ways I have seen around this are (IANAL and I'm probably very imprecise with the following): 1 Dual license with a GPL compatible license where the user is able to choose the license.

2 Re-licensing, the owners have the right to license their code in any fashion that they wish and can also grant a copy of the code under any other license of their choice, even a GPL incompatible one.

3 Plug-in, where the plug-in implements an "interface" of the application's core code to adapt the GPLv2 library to it. Because the plug-in implements the core application's interface it is not viral but the plugin is GPL.

-- DM


On Feb 13, 2008, at 6:44 AM, Grant Ingersoll wrote:

OK, we'll have to see the patch. Don't you just love licensing?  :-)

-Grant

On Feb 13, 2008, at 3:49 AM, [EMAIL PROTECTED] wrote:



Apertium is licensed under the GNU GPL license version 2.

OK, this means that the Jars can not be included in the contrib. The
way to handle this is to have the build script download them for the
user.  See the contrib/db module for how it handles the Berkeley
database.


Apertium is GPL, but that the part that works with Lucene can be
Apache compatible. It uses the Apertium dictionaries and some
Apertium tools to preprocess the files before indexing. The Java
classes that interpret the output of this preprocessing when
indexing are not part of the Apertium project.

--
Felipe

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to