вівторок, 27-чер-2017 16:01:32 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
Hi, Personally, I would like to have translations near the code to ease up the testing and reporting bugs. Sometimes, it is cumbersome to wait for the POT update when you can update it by yourself. On the other hand, if it is such a great obstacle for developers the translations can be separated. However, Rosetta is not the best way for translations though it can be used to make the developers life simpler. ;) 1. It cannot be used for sustainable translations (no fuzzy matching, bad searching capabilities, unstable work on big catalogs like the Inkscape's one) 2. It is hard to use it for uploading offline translations (the queue waiting is unbelivably long, from several hours to days). Please consider some modern services (Weblate with git integration, Pootle, Zanata (can be used instantly on Red Hat servers), or even Transifex). Best regards, Yuri Translator to Ukrainian ------------------------------------------------------------------------------ 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
