Hi Martijn,

Op woensdag 26-09-2007 om 08:49 uur [tijdzone +0200], schreef Martijn Dashorst:
> I think it is still not possible to include (L)GPL based dependencies
> in Apache software: the cannonical list [1] doesn't show GPL v3 as
> being acceptible.

Maybe this thread will convince you that the Apache License and LGPLv3
are perfectly mixable without requiring the end result to be released
under LGPL:

http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200706.mbox/browser

>  Furthermore, the *or newer* clause does not GPL v3
> make.

Umm... what do you mean? LGPLv3 is not a newer version of LGPLv2.1?

> The default gettext translations /are/ IMO GPL, as they are supplied
> by gettext. 

Plain Gettext is GPL, but it's not some process running in the
background. It's a collection of completely independent utilities that
extract strings from source code into a human editable message catalog,
and compile it to a binary format again. It isn't executed during
runtime of the localized application. 

Then there is gettext-commons, that Al Maw linked to. It's a library
that makes it easy to retrieve strings from gettext catalogs in Java. It
is not GPL but LGPL as pointed out previously. 

Are you suggesting that translations become a derivative work of a
GPL'ed $program simply by virtue of having been touched in memory by
said $program?

> derivative works, and are hence (L)GPL licensed. If you want us to use
> gettext to provide our own translations under the ASL, then why not
> continue with the current bundles?

The reason called for .po files (instead of .properties bundles) in the
first place, is that a lot of gettext-based tools exist for translators
to make their task more comfortable.

>  It is not like we are going to
> provide complete translations for all languages.

It would certainly be nice to have a good coverage, though!

regards,

-- 
Reinout van Schouwen




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

Reply via email to