Weblate blog

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).

Full list of changes for 0.7:

• Direct support for GitHub notifications.
• Added support for cleaning up orphaned checks and translations.
• Displays nearby strings while translating.
• Displays similar strings while translating.
• Improved searching for string.

You can find more information about Weblate on it's website, the code is hosted on Github. If you are curious how it looks, you can try it out on demo server. You can login there with demo account using demo password or register your own user.

Weblate is now also being used https://l10n.cihar.com/ as official translating service for phpMyAdmin, Gammu, Weblate itself and others.

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.

Full list of changes for 0.6:

• Added various checks for translated messages.
• Tunable access control.
• Improved handling of translations with new lines.
• Added client side sorting of tables.
• Please check upgrading instructions in case you are upgrading.

You can find more information about Weblate on it's website, the code is hosted on Github. If you are curious how it looks, you can try it out on demo server. You can login there with demo account using demo password or register your own user.

Weblate is now also being used https://l10n.cihar.com/ as official translating service for phpMyAdmin, Gammu, Weblate itself and others.

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.

Full list of changes for 0.5:

• Support for machine translation using following online services:
  • Apertium
  • Microsoft Translator
  • MyMemory
• Several new translations.
• Improved merging of upstream changes.
• Better handle concurrent git pull and translation.
• Propagating works for fuzzy changes as well.
• Propagating works also for file upload.
• Fixed file downloads while using FastCGI (and possibly others).

You can find more information about Weblate on it's website, the code is hosted on Github. If you are curious how it looks, you can try it out on demo server. You can login there with demo account using demo password or register your own user.

Weblate is now also being used https://l10n.cihar.com/ as official translating service for phpMyAdmin, Gammu, Weblate itself and others.

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.

Full list of changes for 0.3:

• Better display of source for plural translations.
• New documentation in Sphinx format.
• Displays secondary languages while translating.
• Improved error page to give list of existing projects.
• New per language stats.

Full list of changes for 0.4:

• Added usage guide to documentation.
• Fixed API hooks not to require CSRF protection.

You can find more information about Weblate on it's website, the code is hosted on Github. If you are curious how it looks, you can try it out on demo server. You can login there with demo account using demo password or register your own user.

Weblate is now also being used https://l10n.cihar.com/ as official translating service for phpMyAdmin, Gammu and others.

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.

Your old usernames and passwords should be valid (in case you've activated the account and used it in last year), but you might want to adjust your profile as the settings were intentionally not imported (many users had corrupted name in Pootle and hope this will let them fix it).

Let's see how many bugs will this switch reveal, but I expect it will work quite smoothly.

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.

Full list of changes includes:

• Improved validation of several forms.
• Warn users on profile upgrade.
• Remember URL for login.
• Naming of text areas while entering plural forms.
• Automatic expanding of translation area.

You can find more information about Weblate on it's website, the code is hosted on Github. If you are curious how it looks, you can try it out on demo server. You can login there with demo account using demo password or register your own user.

PS: As a special bonus, Weblate now comes also with documentation (also available in docs directory in sources).

After about week of (not so heavy) development, I can announce availability of Weblate - web based translation tool with tight Git integration.

The project was started because I was not happy with existing solutions (see my blog post) as all of them was missing some features I find useful. I started with quite simple definition:

Minimalistic web based translation with direct commit to git on each translation made. There is no plan in heavy conflict resolution as these should be primarily handled on git side.

Also the project started with defined list of features:

• Easy web based translation
• Propagation of translations across sub-projects (for different branches)
• Tight git integration
• Usage of Django's admin interface
• Upload and automatic merging of po files
• Links to source files for context

Pretty much all of that is completed right now, however there will be definitely some issues which will need fixing.

All important information about the project are available on it's website, the code is hosted on Github. If you are curious how it looks, you can try it out on demo server. You can login there with demo account using demo password or register your own user.

Please give it some testing as I plan to deploy it on http://l10n.cihar.com/ pretty soon.

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.

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.

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.

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.

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...

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

PS 2: The solution for me is Weblate.