Re: [PATCH 10/25] gettextize: git-merge basic messages

On Fri, Sep 3, 2010 at 17:51, Jonathan Nieder [off-list ref] wrote:

Ævar Arnfjörð Bjarmason wrote:

quoted

Those issues might be a bit hard, but I still can't really see how
managing these files outside of git.git would make things easier.

The translationproject.org thing was a red herring.  As you noticed,
the relevant thing is "outside of git.git".

So imagine there is a git-translations.git project, perhaps.  My
only point was that versioning of translations and versioning of
code can beneficially (in my opinion) be decoupled: with time,
the translations for even _old_ versions of git improve, too.

quoted

maybe we should just use
msgmerge with --no-location.

That would partially alleviate my concerns, and I think we might be
able to get the --add-location output back in actual checkouts with
a "smudge" filter.

After looking at this all closer I found that these line messages
really aren't that important to gettext's operation. So I'm in the
process of removing them from the ab/i18n series.

I documented the new process:
http://github.com/avar/git/raw/ab/i18n/po/README

quoted

But I'd like to coordinate things on this mailing list

[...]

quoted

without some external service being mandatory.

No objection here. :)

Of course, what is convenient for translators and maintainers (i.e.,
not me) takes precedence anyway; I am just throwing out ideas.

Thanks for your thoughtfulness.

Sure, thanks for consistently commenting on all of this. It's great to
get feedback like this.