Hi Martin, can you please detail what issues does the current workflow cause to developers?
What is the proposed way to update the .pot file if translations were split off to a separate repo? Personally, I'm working with the pot/po files, but I suspect I'm in the minority. Regards, ~~helix84 On Tue, Jun 27, 2017 at 4:01 PM, Martin Owens <[email protected]> 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. > > 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 > [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
