7eda31315f
* Refactor calendar-sync feature to be loaded on web. For the web part it just adds new property to enable/disable calendar web integration, disabled by default. * Initial implementation of retrieving google calendar events. * Initial implementation of retrieving microsoft calendar events. * Fixes comments. * Rework to use the promise part of microsoft-graph-client api. * Moves dispatching some actions, fixing comments. * Makes sure we do not initializeClient google-api client multiple times. * Do not try to login when fetching calendar entries. The case where there is a calendar type google selected, but not logged in, trying to login on loading welcome page will show a warning that it tried to open a popup, which was denied by browser. * Updates profile display data on sign in. * Propagate google-api state to calendar-sync only if we use google cal. * Adds sign out action. * Clears the event listener when the popup closes. * Clears calendarIntegrationInstance on signOut. * WIP: UI for calendar settings, refactor auth flows * Clean up some unused constants, functions and exports. * break circular dependency of function and constant * Exports only isCalendarEnabled from functions. * Checks isSignedIn when doing fetchCalendarEntries on web. * address comments List microsoftApiApplicationClientID in undocument config. remove unused SET_CALENDAR_TYPE action use helper for calendar enabled in bootstrap reorder actions reorder imports change order of signin -> set type -> update profile add logging for signout error reword setting dialog desc to avoid redundancy add jsdoc to microsoft button props reorder calendar constants move default state to reducer (not reused anywhere) update comment about calendar-sync due to removal of getCalendarState update comment for getCalendarIntegration remove vague comment alpha order reducer, return default state on reset alpha order persistence registry remove unnecessary getType from apis update comments in microsoftCalendar alpha order google-api exports, use api.get in loadGoogleAPI set jsdoc for google signin props alpha order googleapi methods fix calendartab docs * Moves fetching calendar from APP_WILL_MOUNT to SET_CONFIG. The web part needs configuration in order to refresh tokens (Microsoft). * Fixes storing token expire time and refreshing tokens in Microsoft impl. * Address comments updateProfile changed to getCurrentEmail rename result to results stop storing integration in redux, store if ready for use use existing helpers to parse redirect url * update jsdocs, get google app id from redux * clear integration instead of actual sign out |
||
|---|---|---|
| .. | ||
| 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.