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

Re: [PATCH] Get msgid bug address into .pot file

From: Ben Reser <ben_at_reser.org>
Date: 2004-05-05 17:40:48 CEST

On Wed, May 05, 2004 at 05:25:28PM +0200, Erik Huelsmann wrote:
> It's a requirement for translators; not the build. So I don't see a problem
> in it.

Presumeably though it is a requirement for the RM. Given that my build
machines don't have this release and Debian stable doesn't have this
release, I'd like to avoid having to add one more version for the RM to
worry about upgrading their machine to. Granted this code isn't near a
release. I guess I'm not seeing the specific need for 0.12.

> Besides: Some of our requirements involve releases from weeks ago;
> GNU gettext 0.12 is a year old (next week)...

Not sure what you're refering to. Guess you're refering to neon. Which
the "requirement" for 0.24.5 should be reverted based on a conversation
that happened off-list with Joe Orton. We "need" 0.24.5 for a security
issue, but many distros patch for security issues. So we shouldn't have
configure looking for 0.24.5, we should simply recommend 0.24.5 in our
documentation. So I'll probably be reverting that configure change
soon.

> Plus (and that was my main motivation to agree) it adds an option to turn
> off fuzzy matching. Tobias tells me this functionality has not worked for
> him in the past. Do you have better experiences?

I don't have any specific experience with the fuzzy matching stuff. I'm
just not thrilled with adding more requirements...

-- 
Ben Reser <ben@reser.org>
http://ben.reser.org
"Conscience is the inner voice which warns us somebody may be looking."
- H.L. Mencken
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed May 5 17:41:08 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.