On Tue, Oct 4, 2011 at 00:06, Jonathan Nieder <jrnieder@xxxxxxxxx> wrote: > Ævar Arnfjörð Bjarmason wrote: > >> It's been a long time coming, but here's an initial submission of PO >> files to the po/ directory. This adds some initial and as of yet >> unused translations. > > Neat. I think it's good to figure out what we will do with these > anyway, and we don't have to wait for the infrastructure to do that. I think it's a bit too premature to try to plan this all ahead, why not just take patches to po/ and see what the friction points are, then address those as they arise? The reason I'm submitting this is because: * Other parts of the i18n series depend on there being some PO files for tests etc. * I've had these sitting in my tree for way to long and there's no reason not to stick them in git.git for further improvement. > So, basic questions: > > 1. which branch will be translated? Translations are an end user product, so I think it makes sense to just translate the master when it's near or in the RC phase when you know your work will make it into the end release and be useful to users. > 2. who keeps track of incoming translations? While we could set up some "i18n maintainer" infrastructure why not just have people submit patches to the list like we do for every other file in git? The people maintaining each translation would be the authority on that file so their patches should be fast-tracked once they're seen not te be complete buffoons. > 3. how can we avoid this making "git log -p" output unusable? Well it's already going to be making "git log -p" output unusable for most software projects that use git and any sort of pseudo-generated files, so it sounds like having this in the core and raising an itch to scratch might improve the git user experience for everyone with e.g. an --exclude option to git log. -- 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