Skip to content

Commit

Permalink
blog1 fix
Browse files Browse the repository at this point in the history
  • Loading branch information
comradekingu authored Mar 26, 2021
1 parent b9cc375 commit 594d32d
Showing 1 changed file with 6 additions and 6 deletions.
12 changes: 6 additions & 6 deletions blog1
Original file line number Diff line number Diff line change
@@ -1,15 +1,15 @@
Looking for Pootle alternative

For some time, we use Pootle as online translation tool for phpMyAdmin. It is indeed great tool, but somehow we seem to be hitting more and more issues with it and I feel it really won't fit nicely once we will want to support translations on two divergent branches. Also it's code base is not something easy to understand so that I would be able to fix bugs myself without major effort.
For some time, Pootle has served as a online translation tool for phpMyAdmin. Indeed a great tool, but somehow we are hitting more and more issues with. I feel it really won't fit nicely once we support translations on two divergent branches. Also its codebase is not easily understood to where I would be able to fix bugs myself without major effort.

So this is when I started to look for alternatives. Unfortunately there is nothing I could find what would work in way I want. I've looked at Transifex, Translatewiki, Crowdin and others whose names I've forgotten and I still haven't found what I'm looking for.
This is when I started to look for alternatives. Unfortunately nothing I could find would work the way I want it to. Between looking at Transifex, Translatewiki, Crowdin and yet others, I still haven't found what I'm looking for.

The key feature I want from such system is full integration with git. This means that whatever is changed should be committed to local git branch and merging translations back should be as easy as merging remote branch. I've hacked such thing into Pootle (in quite dirty way), so this is basically workflow we have right now and I'm pretty much happy with that.
The key feature I want from such a system is full integration with Git. This means whatever is changed should be committed to a local Git branch. Merging translations back should be as easy as merging a remote branch. I've hacked such thing into Pootle (in quite an ugly manner). That is the workflow we have right now and I'm pretty much happy with that.

Another thing (which seems to be existing in some tools) is support for simultaneous translation of more branches - if same string exists in more branches, it should be translated in all of them. And last but not least, it should support import of po files allowing users offline translation.
Another thing (which seems a feature of other tools) is support for simultaneous translation of more branches if the same string exists in more branches, it should be translated in all of them. Last but not least, it should support imported PO file from translations made offline.

Thinking about this I'm starting to thing that it should be pretty easy to implement something what I want using existing pieces of software without major effort. I'll probably start to play with Django, translate-tookit and GitPython to see if I can come up with something working reasonably well in few days...
Thinking about this, it should be pretty easy to implement something I want using existing pieces of software, without major effort. I'll probably start to play around with Django, Translate Tookit and GitPython to see if I can come up with something working reasonably well in few days

PS: Anybody working on updated GitPython packages for Debian, looks like I will need them soon :-).

PS 2: The solution for me is Weblate.
The solution for me is Weblate.

0 comments on commit 594d32d

Please sign in to comment.