[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: gettext integration (was Re: [PATCH] Do not use gettextize and i18n round 2 Re: I18n: The gettext proposal)

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-03-30 22:03:38 CEST

On Tue, 2004-03-30 at 13:45, Nicolás Lichtmaier wrote:

> >I just spoke with Justin in IRC, and he's claiming that if we were to
> >require GNU gettext, we'd have to import 28 m4 files. (Is this really
> >true?)
> >
> It's not true. We could
> 1) just add a call to aclocal somewhere (part of normal autoconf
> infrastrcture)

What do you mean by this? That we call out to the gettext a4 files that
live somewhere else on the system?

> 2) write a simpler version of these macros.

This sounds similar to what Justin is proposing...

> But when we add a bunch of
> hand-written subversion specific macros we are adopting a new child to
> feed =).

...but it seems like you're against the idea of writing svn-specific
macros in general. So I'm confused. Can you elaborate on your proposal
to "just add a call to aclocal"?

> But yes, we can target
> any gettext implementation, but doing so will be more complex because
> you never know which level of support each UNIX gettext has.

Is there a minimum set of features that all gettext implementations
support? If so, is it defined anywhere? Surely other projects have
gone down this road before, and have an idea of which gettext features
are portable and which aren't. I'd like to hear more about this.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Mar 30 22:04:40 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.