On Thu, Sep 2, 2010 at 21:13, Jonathan Nieder <jrnieder@xxxxxxxxx> wrote: > Aside: maybe for translation (though not for gettextizing) the idea of > patches that get applied to the development tree is more trouble than > it's worth. GNU sed and some similar projects do not include > translations in the development tree but fetch them from > translationproject.org as part of the "bootstrap" procedure when > building a source tarball or binaries. > > See autoboot in git://git.sv.gnu.org/sed.git for example. I'd prefer to be able to submit translations directly to git.git, and build a localized git with "make" and no network access. Most programs that use gettext do this, sed seems to be an exception, and actually I've never seen anyone do it like that. Some maintain their translations in some web interface, but I haven't seen a project that doesn't commit them *at all*. I can't see why translations in the tree (in po/) should be any trouble at all for us. What sort of issues do you see that the sed.git model might solve? -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html