Open ilyaspiridonov opened 4 years ago
I second this i am using it to translate now via my repository works amazing.
I needed to update the directories structure (move from directories to branches) to have support for Gitbook.com (which is where we publish the documentation) but this seems to go against the logic of GitLocalize, as they expect the translation to land in a language-defined directory (or file). Still looking for a way around this...
I don't think I can reliably link to the conversation, so here is a screenshot of my conversation with the GitLocalize leader about this topic:
Please consider using GitLocalize to manage translations. It's free, supports .md and syncs with GitHub directly.