jiti-meet/lang
Ingo Bauersachs a38e85b39c Update languages.json 2016-07-19 22:51:38 +02:00
..
languages-bg.json Commit from translate.jitsi.org by user emcho.: 180 of 180 strings translated (0 fuzzy). 2016-04-20 23:06:12 +00:00
languages-de.json Commit from translate.jitsi.org by user ibauersachs.: 250 of 250 strings translated (0 fuzzy). 2016-07-19 20:37:10 +00:00
languages-es.json Commit from translate.jitsi.org by user emcho.: 180 of 180 strings translated (0 fuzzy). 2016-04-25 19:29:18 +00:00
languages-fr.json Commit from translate.jitsi.org by user ibauersachs.: 250 of 250 strings translated (0 fuzzy). 2016-07-19 20:37:30 +00:00
languages-hy.json New files added from translate.jitsi.org based on templates 2016-05-05 10:45:10 +00:00
languages-it.json Commit from translate.jitsi.org by user ibauersachs.: 159 of 159 strings translated (0 fuzzy). 2015-03-24 15:35:05 +00:00
languages-oc.json New files added from translate.jitsi.org based on templates 2016-04-25 17:14:01 +00:00
languages-pt_BR.json Commit from translate.jitsi.org by user ibauersachs.: 250 of 250 strings translated (0 fuzzy). 2016-07-19 20:38:09 +00:00
languages-sk.json Commit from translate.jitsi.org by user ibauersachs.: 175 of 175 strings translated (0 fuzzy). 2015-09-07 13:04:09 +00:00
languages-sl.json Commit from translate.jitsi.org by user ibauersachs.: 172 of 173 strings translated (0 fuzzy). 2015-08-19 19:58:21 +00:00
languages-sv.json Commit from translate.jitsi.org by user ibauersachs.: 175 of 180 strings translated (0 fuzzy). 2015-11-09 13:01:12 +00:00
languages-tr.json Commit from translate.jitsi.org by user ibauersachs.: 135 of 135 strings translated (0 fuzzy). 2015-03-10 10:10:08 +00:00
languages.json Update languages.json 2016-07-19 22:51:38 +02:00
main-bg.json Commit from translate.jitsi.org by user emcho.: 180 of 180 strings translated (0 fuzzy). 2016-04-20 23:06:12 +00:00
main-de.json Commit from translate.jitsi.org by user ibauersachs.: 250 of 250 strings translated (0 fuzzy). 2016-07-19 20:37:10 +00:00
main-es.json Commit from translate.jitsi.org by user emcho.: 180 of 180 strings translated (0 fuzzy). 2016-04-25 19:29:18 +00:00
main-fr.json Commit from translate.jitsi.org by user ibauersachs.: 250 of 250 strings translated (0 fuzzy). 2016-07-19 20:37:30 +00:00
main-hy.json New files added from translate.jitsi.org based on templates 2016-05-05 10:45:10 +00:00
main-it.json Commit from translate.jitsi.org by user ibauersachs.: 159 of 159 strings translated (0 fuzzy). 2015-03-24 15:35:05 +00:00
main-oc.json New files added from translate.jitsi.org based on templates 2016-04-25 17:14:01 +00:00
main-pt_BR.json Commit from translate.jitsi.org by user ibauersachs.: 250 of 250 strings translated (0 fuzzy). 2016-07-19 20:38:09 +00:00
main-sk.json Commit from translate.jitsi.org by user ibauersachs.: 175 of 175 strings translated (0 fuzzy). 2015-09-07 13:04:09 +00:00
main-sl.json Commit from translate.jitsi.org by user ibauersachs.: 172 of 173 strings translated (0 fuzzy). 2015-08-19 19:58:21 +00:00
main-sv.json Commit from translate.jitsi.org by user ibauersachs.: 175 of 180 strings translated (0 fuzzy). 2015-11-09 13:01:12 +00:00
main-tr.json Commit from translate.jitsi.org by user ibauersachs.: 135 of 135 strings translated (0 fuzzy). 2015-03-10 10:10:08 +00:00
main.json Change global font, unify fonts, colors and more 2016-06-24 14:09:34 -05:00
readme.md Rename Translation.md to readme.md 2016-06-15 11:45:03 +02:00

readme.md

Jitsi Meet Translation

Jitsi Meet uses i18next library for translation. i18next uses separate json files for each language.

Translating Jitsi Meet

The translation of Jitsi Meet is integrated with Pootle. You can translate Jitsi Meet via our Pootle user interface on http://translate.jitsi.org.

WARNING: Please don't create or edit manually the language files! Please use our Pootle user interface!

Development

If you want to add new functionality for Jitsi Meet and you have texts that need to be translated please use our translation module. It is located in modules/translation. You must add key and value in main.json file in English for each translatable text. Than you can use the key to get the translated text for the current language.

WARNING: Please don't change the other language files except main.json! They must be updated and translated via our Pootle user interface!

You can add translatable text in the HTML:

  • via attribute on HTML element - add data-i18n attribute with value the key of the translatable text.
<span data-i18n="dialog.OK">OK</span>

You can also use APP.translation.generateTranslationHTML(key, options) to get this HTML code as Javascript string.

APP.translation.generateTranslationHTML("dialog.OK") // returns <span data-i18n="dialog.OK">OK</span>

The value in the options parameter will be added in data-i18n-options attribute of the element.

Note: If you dynamically add HTML elements don't forget to call APP.translation.translateElement(jquery_selector) to translate the text initially.

  • via Javascript string - call APP.translation.translateString(key, options). You can use that method to get the translated string in Javascript and then attach it in the HTML.
APP.translation.translateString("dialog.OK") // returns the value for the key of the current language file. "OK" for example. 

For the available values of options parameter for the above methods of translation module see i18next documentation.

Note: It is useful to add attributes in the HTML for persistent HTML elements because when the language is changed the text will be automatically translated. Otherwise you should call APP.translation.translateString and manually change the text every time the language is changed.