You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Nicolás Lichtmaier <ni...@reloco.com.ar> on 2004/03/29 01:54:12 UTC

I18n with gettext

Would you like me to add i18n using gettext? Would it be included?

Besides, I see that files do not include <config.h> (which is named 
svn_private_config.h). Why is that? And the ones which do include it, 
they include it wrongly, after every other header. Shouldn't every files 
have the classic:

#ifdef HAVE_CONFIG_H
#include <config.h>
#endif

(Or "svn_private_config.h", but note that the define will always be 
HAVE_CONFIG_H, which IMO made renaming this file not very recommendable).


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: I18n with gettext

Posted by Nuutti Kotivuori <na...@iki.fi>.
C. Michael Pilato wrote:
> "No" (... gettext is GPLed, and that's incompatible with the
> Subversion license).

David Waite wrote:
> COPYING says GPL, and RMS has used gettext as the primary example of
> a library which was a good choice for the GPL license vs LGPL.

,----[ http://www.delorie.com/gnu/docs/gettext/gettext_164.html ]
| * Dependencies over the GPL or LGPL
| 
| Some people wonder if using GNU gettext necessarily brings their
| package under the protective wing of the GNU General Public License or
| the GNU Library General Public License, when they do not want to make
| their program free, or want other kinds of freedom. The simplest
| answer is "normally not".
| 
| The GNU gettext library, i.e. the contents of libintl, is covered by
| the GNU Library General Public License. The rest of the GNU gettext
| package is covered by the GNU General Public License.
| 
| The mere marking of localizable strings in a package, or conditional
| inclusion of a few lines for initialization, is not really including
| GPL'ed or LGPL'ed code. However, since the localization routines in
| libintl are under the LGPL, the LGPL needs to be considered. It gives
| the right to distribute the complete unmodified source of libintl even
| with non-free programs. It also gives the right to use libintl as a
| shared library, even for non-free programs. But it gives the right to
| use libintl as a static library or to incorporate libintl into another
| library only to free software.
`----

We use Neon as LGPL as well - so there *should* be no problem.

Then again, even though that is from the gettext documentation, I am
not entirely convinced that trusting that is enough.

-- Naked


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: I18n with gettext

Posted by Branko Čibej <br...@xbc.nu>.
Nicolás Lichtmaier wrote:

> David Waite wrote:
>
>> COPYING says GPL, and RMS has used gettext as the primary example of
>> a library which was a good choice for the GPL license vs LGPL.
>
>
>
> It's LGPL. In fact it's included in GNU libc, which is LGPL.

Glibc is *not* LGPL. It is GPL with an exception that allows it to be
linked with closed-source code. Also, the /standalone/ version of
gettext has always had a different license than the glibc version (i.e.,
GPL without the exception).

*however*

Sometime last year RMS was finally persuaded to relent, so the latest
releases of gettext are now LGPL. IIRC the KDE guys threatened to pull
the plug on GNU/Linux support if the license wasn't changed, or something.


-- 
Brane Čibej   <br...@xbc.nu>   http://www.xbc.nu/brane/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: I18n with gettext

Posted by Nicolás Lichtmaier <ni...@reloco.com.ar>.
David Waite wrote:

> COPYING says GPL, and RMS has used gettext as the primary example of a 
> library which was a good choice for the GPL license vs LGPL.


It's LGPL. In fact it's included in GNU libc, which is LGPL.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: I18n with gettext

Posted by David Waite <ma...@akuma.org>.
COPYING says GPL, and RMS has used gettext as the primary example of a 
library which was a good choice for the GPL license vs LGPL.

-David Waite

On Mar 28, 2004, at 7:19 PM, Nicolás Lichtmaier wrote:

>
>>> Would it be included?
>>>
>>
>> "No" (... gettext is GPLed, and that's incompatible with the
>>      Subversion license).
>>
>
> Gettext is LGPLed.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org


Re: I18n with gettext

Posted by Nicolás Lichtmaier <ni...@reloco.com.ar>.
>>Would it be included?
>>    
>>
>
>"No" (... gettext is GPLed, and that's incompatible with the
>      Subversion license).
>  
>

Gettext is LGPLed.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: I18n with gettext

Posted by "C. Michael Pilato" <cm...@collab.net>.
Nicolás Lichtmaier <ni...@reloco.com.ar> writes:

> Would you like me to add i18n using gettext? 

"No" (because you'd be wasting your time, since ...)

> Would it be included?

"No" (... gettext is GPLed, and that's incompatible with the
      Subversion license).

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org