Weblate-Blog
Weblate 0.7
Continuing at same pace (one release every two days), I can announce Weblate 0.7. The major change is built in full text search and displaying of context for currently translated message (either based on location in po file or by string similarity based on full text data).
Weblate 0.6
Continuing with fast release pace for Weblate, I've just released version 0.6. It brings few bug fixes adds quality checks for translations and configurable access control.
Weblate 0.5
Continuing with fast release pace for Weblate, I've just released version 0.5. It brings lot of bug fixes (thanks for everybody who has provided feedback), lot of new translations (thanks to translators) and as a special bonus it can use few machine translation services.
Weblate 0.4
Yesterday, I've finalized Weblate 0.4. It improved handling of plural strings, added documentation and implemented support for secondary languages. If you ask for 0.3, well I managed to release two versions in the day, but I expect to slow down this pace.
l10n.cihar.com switched to Weblate
I've just switched https://l10n.cihar.com/ to Weblate as I think it's stable enough to replace Pootle installation there. This change immediately affects translation of all projects which were done there - phpMyAdmin, Gammu, Wammu, GePeS or Ukolovnik. In addition Weblate itself is also being translated there.
Weblate 0.2
Thanks to great feedback I've received on Weblate, I've decided to release 0.2 version quite soon to fix things where people complained most. It improves validation of some forms and there are lot of improvements in editing translations, especially plurals.
Announcing Weblate
After about week of (not so heavy) development, I can announce availability of Weblate - web based translation tool with tight Git integration.
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.