d8cd3e75b4
* feat(quality-slider): initial implementation - Add new menu button with an Inline Dialog slider for selecting received video quality. - Place P2P status in redux store for the Inline Dialog to display a warning about not respecting video quality selection. - Respond to data channel open events by setting receive video quality. This is for lonely call cases where a setting is set before the data channel is open. - Remove dropdown menu from video status label and clean up related js and css. * first pass at addressing feedback - Move VideoStatusLabel to video-quality directory. - Rename VideoStatusLabel to VideoQualityLabel. - Open VideoQualitydialog from VideoQualityLabel. - New CSS for making VideoQualityLabel display properly. - Do not render VideoQualityLabel in filmstrip only instead of hiding with css. - Remove tooltip from VideoQualityLabel. - Show LD, SD, HD labels in VideoQualityLabel. - Remove action SET_LARGE_VIDEO_HD_STATUS from conference. - Create new action UPDATE_KNOWN_LARGE_VIDEO_RESOLUTION in large-video. - Move VideoQualityButton into video-quality directory. - General renaming (medium -> standard, menu -> dialog). - Render P2P message between title and slider. - Add padding to slider for displacement caused by P2P message's new placement. - Fix display issue with VideoQualityButton displaying out of line in the primary toolbar. * second pass at addressing feedback - Fix p2p inline message color - Force labels to break on words - Resolve rebase issues, including only dispatching quality update on change. Before there was double calling of dispatch produced by an IE11 workaround. This breaks now when setting audio only mode to true twice. - Rename some instances of quality to definition * rename to data channel opened * do not show p2p in audio only * stop toggle audio only icon automatically * remove fixme about toolbar button * find closest resolution for label * toggle dialog on button click * redo last commit for both button and label |
||
|---|---|---|
| .. | ||
| languages-bg.json | ||
| languages-cs.json | ||
| languages-de.json | ||
| languages-eo.json | ||
| languages-es.json | ||
| languages-fr.json | ||
| languages-hy.json | ||
| languages-it.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-bg.json | ||
| main-cs.json | ||
| main-de.json | ||
| main-eo.json | ||
| main-es.json | ||
| main-fr.json | ||
| main-hy.json | ||
| main-it.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.