This page is a translated version of the page ToolTranslate and the translation is 23% complete.

Це — посібник для інструмента ToolTranslate. Можете його перекласти!

ToolTranslate у дії


Many tools on Toolforge lack interface translations, that is, they are only available in one language, usually English. Even tools that support multiple languages in the interface use clunky methods for adding new languages and translations. ToolTranslate offers a centralized, user-friendly way for The Community (TM) to provide translations for tools. Tools need to support this mechanism, that is, they need to be "worked over" once to use dynamic rather than static text in the interface. Original blog post.


  1. Перейдіть до інструменту
  2. Якщо потрібно, авторизуйте цей інструмент
  3. Виберіть інструмент для перекладу з випадного списку зверху або списку на головній сторінці
  4. Виберіть або додайте мову для перекладу
  5. Двічі швидко клацніть на "комірку", де має бути ваш новий переклад, або переклад, який ви хочете покращити
  6. Введіть текст. Ви можете використовувати HTML (без JavaScript!). Там може бути пропозиція для перекладу з іншого інструменту з тим самим "ключовим іменем", ви можете використовувати її як основу для вашого тексту.
  7. Натисніть "ОК". Готово! Кешування браузера може призвести до того, що переклади не відображатимуться в перекладеному інструменті, доки ви не перезавантажите його.



Translations are stored in a database on Toolforge. Old revisions of translations are kept, and translations are attributed to the respective editor. (A "recent changes" tool is available.)

To simplify access to translation data, all translations are also stored in JSON files, which are updated on every change. Example "demotool1":

  • toolinfo.json, a JSON file with information about the tool
  • en.json, the JSON file containing the English translation of that tool. Other languages work in the same manner, with the respective language code

There is also a JSON file with all valid languages.

База даних

The source data is stored in the s53069__tooltranslate_p database on tools-db on Toolforge (mysql --defaults-file=~/ -h tools-db s53069__tooltranslate_p). Data can be fetched from there as well if needed. Following tables are available:

  • tool
    • id | name | label | url | owner
  • translation
    • id | tool_id | language | key | json | user | timestamp | current


HowTo: PHP

There is a PHP class that you can include on Toolforge, like so:

require_once ( "/data/project/tooltranslate/public_html/tt.php") ;

You can then instantiate the class:

$tt = new ToolTranslation ( array ( 'tool' => 'your_tool_key' , 'language' => 'de' , 'fallback' => 'en' , 'highlight_missing' => true ) ) ; // <span lang="en" dir="ltr" class="mw-content-ltr">Everything except 'tool' is optional</span>

Direct usage

There are two ways of getting interface translations in PHP. One is directly getting a translated string

print "<p>" . $tt->t('translation_key') . "</p>" ;

But this has the disadvantage that the translation cannot be changed without reloading the page.

Use via JS

You can instead add HTML "translation tags" (see above), and have the class add the necessary JS invocation. Another advantage is that the PHP class does not need to load any translation files if you never use the "direct" translation above. To use HTML/JS translation, the <head> section of your pages' HTML needs to contain

<script src="">

(You will also need jQuery.) When generating the page, instead of the above, write:

print "<p tt='translation_key'></p>" ;

Somewhere in the output (maybe towards the end), you will need to add the invocation code:

print $tt->getJS() ;

This will initialize the required JS, reproducing the parameters used in the PHP instance (fallback language etc.). If you want a "translation dropdown", add a wrapper element in your HTML code

<div id='tooltranslate_wrapper'></div>

then give the jQuery accessor as a parameter to the getJS method call:

print $tt->getJS('#tooltranslate_wrapper') ;

See this tool for a working example.