On Sun, Jul 02, 2017 at 10:13:59AM +0200, Martin Owens wrote: > Thanks Bryce, > > >From what we can tell, the pot file is regenerated in-situe when > running make only sometimes. Mostly it doesn't, but then when certain > files change, it does. > > So if we want such a thing, we should decide if we want it in the > general make command or not. > > But the normal make probably shouldn't ever change the repository.
What do the diffs look like when the .pot gets changed? Is there some autogenerating code that's triggering it? Or is pot depending on something volatile in the source code (e.g. the line number of some chunks in the code file? Or something else? Or could the pot be depending on something git-specific (i.e. did this change when we moved to git, and didn't do it with bzr for some reason?) Bryce > Martin, > > On Sat, 2017-07-01 at 10:52 -0700, Bryce Harrington wrote: > > On Tue, Jun 27, 2017 at 04:01:32PM +0200, Martin Owens wrote: > > > > > > Dear Translators, > > > > > > I'm at the Inkscape Hackfest here in Paris and we were wondering if > > > it > > > would be good or bad to remove the pot file and po files from the > > > master branch and separate them out into their own repository. > > > > > > The pot file gets modified on each make, and it's causing some > > > minor > > > issues for developers. So the preference for developers is for > > > removal. > > Did it get sorted out why the .pot file is getting modified on each > > make? It didn't used to do that, so it seems the root of the problem > > is > > this. > > > > I'll defer to translators but from a release perspective I've been > > given > > to understand that having the .pot and .po files with the source file > > is > > strongly preferred. > > > > > > > > But this depends very heavily on HOW translations for inkscape are > > > done. If they are done 'in-place' or if translators expect to use a > > > service like launchpad translations which keeps track of > > > everything. > > There had been a discussion about using launchpad translations when > > we > > migrated to LP years ago, but what I recall was that the general > > consensus was that it was not desireable to use and unlikely to > > stimulate translation activity, so it was never formally adopted. > > > > > > > > Please let us know what you would like us to do with pot and po > > > files > > > regarding development. > > Keep me apprised of what decision was reached here, this will affect > > release management if it's changed... > > > > Bryce > > > > > > > > Best Regards, Martin Owens > > > > > > ----------------------------------------------------------------- > > > ------------- > > > Check out the vibrant tech community on one of the world's most > > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > _______________________________________________ > > > Inkscape-translator mailing list > > > [email protected] > > > https://lists.sourceforge.net/lists/listinfo/inkscape-translator ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Inkscape-translator mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/inkscape-translator
