b7b43e8d9c
- Change "features/chat" to support listening for new chat messages and storing them, removing that logic from conference.js. - Combine chat.scss and side_toolbar_container.css, and remove unused scss files. Chat is the only side panel so the two concepts have been merged. - Remove direct access to the chat feature from non-react and non-redux flows. - Modify the i18n translate function to take in an options object. By default the option "wait" is set to true, but that causes components to mount after the parent has been notified of an update, which means autoscrolling down to the latest rendered messages does not work. With "wait" set to false, the children will mount and then the parent will trigger componentDidUpdate. - Create react components for chat. Chat is the side panel plus the entiren chat feature. ChatInput is a child of Chat and is used for composing messages. ChatMessage displays one message and extends PureComponent to limit re-renders. - Fix a bug where the toolbar was not showing automatically when chat is closed and a new message is received. - Import react-transition-group to time the animation of the side panel showing/hiding and unmounting the Chat component. This gets around the issue of having to control autofocus if the component were always mounted and visibility toggled, but introduces not being able to store previous scroll state (without additional work or re-work). |
||
---|---|---|
.. | ||
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-zhTW.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-zhTW.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.