c353e9377f
* feat(tile-view): initial implementation for tile view - Modify the classname on the app root so layout can adjust depending on the desired layout mode--vertical filmstrip, horizontal filmstrip, and tile view. - Create a button for toggling tile view. - Add a StateListenerRegistry to automatically update the selected participant and max receiver frame height on tile view toggle. - Rezise thumbnails when switching in and out of tile view. - Move the local video when switching in and out of tile view. - Update reactified pieces of thumbnails when switching in and out of tile view. - Cap the max receiver video quality in tile view based on tile size. - Use CSS to hide UI components that should not display in tile view. - Signal follow me changes. * change local video id for tests * change approach: leverage more css * squash: fix some formatting * squash: prevent pinning, hide pin border in tile view * squash: change logic for maxReceiverQuality due to sidestepping resizing logic * squash: fix typo, columns configurable, remove unused constants * squash: resize with js again * squash: use yana's math for calculating tile size |
||
|---|---|---|
| .. | ||
| languages-az.json | ||
| languages-bg.json | ||
| languages-cs.json | ||
| languages-de.json | ||
| languages-eo.json | ||
| languages-es.json | ||
| languages-fa.json | ||
| languages-fr.json | ||
| languages-hu.json | ||
| languages-hy.json | ||
| languages-it.json | ||
| languages-ja.json | ||
| languages-kab.json | ||
| languages-ko.json | ||
| languages-nb.json | ||
| languages-oc.json | ||
| languages-pl.json | ||
| languages-ptBR.json | ||
| languages-ru.json | ||
| languages-sk.json | ||
| languages-sl.json | ||
| languages-sv.json | ||
| languages-tr.json | ||
| languages-vi.json | ||
| languages-zhCN.json | ||
| languages.json | ||
| main-az.json | ||
| main-bg.json | ||
| main-cs.json | ||
| main-de.json | ||
| main-eo.json | ||
| main-es.json | ||
| main-fa.json | ||
| main-fr.json | ||
| main-hu.json | ||
| main-hy.json | ||
| main-it.json | ||
| main-ja.json | ||
| main-kab.json | ||
| main-ko.json | ||
| main-nb.json | ||
| main-oc.json | ||
| main-pl.json | ||
| main-ptBR.json | ||
| main-ru.json | ||
| main-sk.json | ||
| main-sl.json | ||
| main-sv.json | ||
| main-tr.json | ||
| main-vi.json | ||
| main-zhCN.json | ||
| main.json | ||
| readme.md | ||
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.
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.