I pushed a few improvements to the TermBase. One of these improvements is the ability to download your TermBase as a TBX File.
TBX (TermBase eXchange) is an industry standard for exchanging glossaries between translation tools.
The green button will let you download all the language pairs in a single TBX file. You can also download specific language pairs by clicking on the small button to the right.

This improvement is also available as an API endpoint: the TermBase to TBX endpoint.
I added two new API endpoints to WebTranslateIt’s API lately: zip_file and top_translators.
The zip_file endpoint serves all your project’s language files as a zip archive. It also takes an optional ?locale=xx parameter to serve all your project’s language files for in a specific locale. This feature has been added to the File Manager as well.
The top_translators endpoint serves a list of most active translators in a project. Top Translators is a list of the most active contributors to your translation project.
I hope you will find these new endpoints useful. Thank you for using WebTranslateIt.
WebTranslateIt’s integrated dictionary just got updated and now use WordReference.com as a source.
WordReference is one of the best dictionary website on the web and is well-liked among the translator’s community. It currently supports the following language pairs:
It is perfectly integrated to WebTranslateIt, so you can lookup words without leaving the translation interface.
Even better: you can request a definition for any word in the translation interface: select a word, press the d key and get definitions and translations without leaving WebTranslateIt.

I hope you will find this improvement to WebTranslateIt useful.
I just released Top Translators. This feature is a page which ranks the most active translators on a project. This is useful to reward the most active contributors on open-source or crowd-sourced translation projects.
You can filter this list by team, or see the user’s ranking across all language teams.
I hope you will find this feature useful. Thank you for using WebTranslateIt.
I just released an important update to WebTranslateIt’s API.
This update gives you full control on your project TermBase, its terms and its translations. It adds 8 new endpoints:
You can use this API to import and export all the terms and translations from a TermBase.
I hope you will find this update useful. Thank you for using WebTranslateIt.
I rolled out a few improvements to WebTranslateIt this week: Autosave, Webhooks, new keyboard shortcuts…
Autosave is a new option available in the translation toolbar.

It’s turned off by default. When you turn it on, translations are automatically saved as you type them. No need to click on save or type the Ctrl+s keyboard shortcut.
You can now setup a WebHook to a project on WebTranslateIt.
WebHooks are a way to tell WebTranslateIt to call a script on one of your own web servers whenever a translation was made and react in any way your want. WebHooks can be thought of as push notifications.
Setting up a WebHook is easy: in your project settings, a new “WebHook” section will let you enter the URL of your server to call.

Once this is setup WebTranslateIt will call the URL provided whenever a translation is saved on your project.
For detailed and technical information, please visit the documentation section about WebHooks.
I really like keyboard shortcuts. It’s a great way to save time while translating. You can learn more about keyboard shortcuts by hitting the h key anywhere in WebTranslateIt.
The two new keyboard shortcuts I added this week are really handy.
When editing a translation, the Tab key will save the current translation and jump to the next one.
You can also save the current translation and jump to the previous one by using Shift + Tab.
You can read more about all these improvements and bug fixes in the changelog.
I hope you will find these improvements useful. Thank you for using WebTranslateIt.
WebTranslateIt now supports Adobe FrameMaker .mif files.
.mif (Maker Interchange Format) is a proprietary markup language associated with Adobe’s FrameMaker product for technical document preparation.
I am also currently testing support for LaTeX documents, a widely used file format in academia.
WebTranslateIt now supports more than 34 different linguistic file formats.
I added 2 new batch operations to WebTranslateIt: Translate complete matches and Add Label.
Translate complete matches is a batch operation that looks for repetitions within your project (repetitions are segments matching entirely another segment which is already translated). When possible, this batch operation automatically translates the segment using the project translation memory. When no match was found, it leaves the translation empty.
Add Label is a batch operation to add a specific label to the selected strings. It is also possible to remove labels in batch.
WebTranslateIt now supports Docbook files.
Docbook files are intended to be used for writing technical documents related to computer hardware and software but it can be used for any other sort of documentation.
Docbook is one of the 32 different linguistic file formats you can translate with WebTranslateIt.
i18next is a third-party i18n Javascript library you might find useful for localizing Javascript in your application.
Add the i18next.js after the jquery JavaScript.
<script type="text/javascript" src="jquery-1.6.4.min.js"></script> <script type="text/javascript" src="i18next-[version].js"></script>
Add your resourcefile under /locales/en-US/translation.json. Translations are stored in a JSON hash compatible with WebTranslateIt’s JSON.
{
"app": {
"name": "i18n"
},
"creator": {
"firstname": "Jan",
"lastname": "Mühlemann"
}
}
Init and use the module:
$.i18n.init({}, function(t) { // will init i18n with default settings and set language from navigator
var appName = t('app.name'); // -> i18n
var creator = t('creator.firstname') + ' ' + t('creator.lastname'); // -> Jan Mühlemann
});