[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: Erik Huelsmann <e.huelsmann_at_gmx.net>
Date: 2004-05-05 18:29:32 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.

Ok. I wasn't that far yet: I have no idea what the relation between this
work and the release process will be. As it stands a release including
subversion.pot can only be generated on GNU gettext Makefile based
systems... For now that leads me to claiming that it won't be included.

That leaves the RM with the task of including the *.po files. Those are in
the tree and need no changes at the time of release. (Surely we won't
require the RM to fill the missing translations in the Polish po.. ;-)

> 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.

Point taken.

I'll leave it to Tobias to comment on the need to have the
--no-fuzzy-matching. The problem I found is that 0.12 and up will always
generate the "Report-Msgid-Bugs-To: " line. If possible, I'd like to have
consistent po file updates. If both pre- and post-0.12 versions are used
they will be alternatingly installing and removing the line..

bye,

Erik.

-- 
NEU : GMX Internet.FreeDSL
Ab sofort DSL-Tarif ohne Grundgebühr: http://www.gmx.net/dsl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed May 5 18:29:55 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.