Hi Martin,
what kind of issues does it cause, and how would the pot and po files be kept updated then in their separate repo (preferably automatically on each commit)?
I personally don't care too much if it's a separate repo or not (e.g. Eduard and I have been using a dedicated github repo last time), as long as - when I'm building my own Inkscape version - I can easily pull in the necessary translation files, perhaps using a script or a specific option for cmake...
Using a dedicated service with a web interface would help pull in more contributors, I think. For myself, I'm happy with using lokalize and git, and to have the corresponding source files at hand - this is also better when you want to check what the translations look like, what they really refer to (and if they fit length-wise).
(I think there is currently no launchpad translations service in effect. Or is there?...)
Maren
Am 27.06.2017 um 16:01 schrieb Martin Owens:
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.
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.
Please let us know what you would like us to do with pot and po files regarding development.
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 Inkscape-translator@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-translator