Re: About the license of L10n products
Gervase Markham <[email protected]> Mon, 12 Oct 2009 12:01:19 +0100
| Newsgroups | gmane.comp.mozilla.license |
|---|---|
| Message-ID | <[email protected]> |
On 12/10/09 11:20, Axel Hecht wrote: >> 1. KDE and GNOME includes many projects. Does each project have their own >> license, or only projects which are published as a specific license >> like as GPL >> or BSD? For example, every L10n works on Launchpad are under BSD, >> aren't them? You would need to ask the KDE and GNOME projects, but my understanding is that each project has its own licence - although most use the GPL. >> 2. If each project has their own license for their L10n works, how can >> I handle >> those if I want to collect them and reproduce something using them. >> I'm making a glossary using many L10n works from many projects. You may end up finding that this is not possible. It depends on which sources you use, and the licenses attached to them. >> 3. Can I publish and share my glossary under GPL? If I can, which version >> should I use, v3.0 or v2.0? There are several licenses, for GNOME, KDE >> and >> GIMP are GPL, LGPL for OpenOffice, Firefox has MPL and BSD for Launchpad. Firefox and Mozilla code, including the Korean translation, is available under your choice of three licences - the MPL, the LGPL or the GPL. So if you are looking to make your glossary GPLed, then you can include information gained from Firefox. However, you would have to consider the possibility that your glossary could only be _used_ by GPLed projects in the case, because use of it might make the target translation a derivative work of the glossary. Gerv