You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by kf...@collab.net on 2004/03/30 16:20:26 UTC
Re: [PATCH] Do not use gettextize and i18n round 2 Re: I18n: The gettext proposal
Justin Erenkrantz <ju...@erenkrantz.com> writes:
> > That's not necessarily our problem, as long as we don't ourselves
> > distribute the static binary. If a user wishes to create a static
> > binary and use it without distributing it, the LGPL restrictions on
> > distributing static binaries don't come into play.
>
> Well, I thought I just saw a thread about trying to promote creating
> binaries for Subversion rather than distributing source. *shrug*
Not "rather than" but "in addition to", yeah.
(I'm reading the LGPL and gettext's use of it carefully now, would
like a first-hand understanding of the restrictions here.)
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] Do not use gettextize and i18n round 2 Re: I18n: The gettext proposal
Posted by "Peter S. Housel" <ho...@acm.org>.
<kf...@collab.net> writes:
> Justin Erenkrantz <ju...@erenkrantz.com> writes:
> > > That's not necessarily our problem, as long as we don't ourselves
> > > distribute the static binary. If a user wishes to create a static
> > > binary and use it without distributing it, the LGPL restrictions on
> > > distributing static binaries don't come into play.
> >
> > Well, I thought I just saw a thread about trying to promote creating
> > binaries for Subversion rather than distributing source. *shrug*
>
> Not "rather than" but "in addition to", yeah.
>
> (I'm reading the LGPL and gettext's use of it carefully now, would
> like a first-hand understanding of the restrictions here.)
The gettext file format is documented in the gettext info files; it's not
exactly rocket science. I suggest writing a new gettext runtime that could
be included in apr or apr-utils; the build could continue to use the GNU
gettext utilites, of course. This approach would also allow better
integration with apr_iconv and the like.
-Peter-
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org