i managed to get a few others - probs the best i found was gitlab.com/translate.apps/...
@unho im wondering if we can keep github as a mirror, disable tickets/wiki etc on github and put a notice to preferably make PRs on gitlab
there is a bunch of CI to figure out too
I like the mirror idea.
Moving from one proprietary environment to another doesn't really seem to offer much. It doesn't really matter who owns github does it?
I don't really see much benefits from moving from GitHub to GitLab - it's still third party commercial service which can be gone or changing TOS at any point. There is nothing wrong on GitHub right now and moving things around will IMHO just confuse users who will be still looking in the old location.
But if you feel it's good thing to do, feel free to go ahead
Hi! I got hit by this bug: translate/pootle#4762 and I would like to fix it (or at least try to workaround it somehow on my Pootle instance). I tried to find the place where XLIFF file are serialised (when running with fs sync), but I can't seem to find any XLIFF specific code in Pootle project. Can someone give me a hint, where I should start ?
Hi! Chatting to a developer about the i18n process today and suggested that for error messages from his program, he ensure that there is an untranslated error code so that there is still some hope of asking google for assistance with an error. (e.g. "Could not reach server [E123]"). He was receptive to the idea but wanted to know if I could point to some documentation on best practices. Any thoughts?