Zen

Traduction

Anglais type: Title ###
Use translations in front-end code
0/340 · 34

Connectez-vous pour enregistrer vos traductions.

Anglais Persan Actions
Create an account: https://weblate.framasoft.org/accounts/register/
 
Validate your email and follow the link sent
 
Create your password and setup your account
 
Go to the plugin project page: https://weblate.framasoft.org/projects/peertube-livechat/peertube-plugin-livechat/
 
Choose the locale you want to translate
 
Just translate missing sentences, or correct the ones that seems incorrect to you.
 
There might be some «very technical» strings. If you are not 100% sure of the meaning, or of your translation, you better not translate it, so it will display in english.
 
ConverseJS translations
 
This plugin relies on [ConverseJS](https://conversejs.org/) for the chat front-end. ConverseJS has its own translations, on its own [weblate instance](https://hosted.weblate.org/projects/conversejs/#languages). You can also translate directly in the code repository. For more information, check [ConverseJS translations documentation](https://conversejs.org/docs/html/translations.html).
 
Adding a new locale
 
If you think there is a missing locale, please check first if it is handled in Peertube. If so, you can [open an issue](https://github.com/JohnXLivingston/peertube-plugin-livechat/issues) to ask for it.
 
Adding new strings / use translations in the code
 
If you are working on new features, and need new strings, you can create them directly in Weblate. The english version is mandatory. Start with it.
 
Each string is linked to a key (for example `use_chat`). Choose an explicit key in english, lower case.
 
If you have to test new strings without waiting for a Weblate merge, you can modify `languages/*.yml` files, but avoid to commit these changes (to minimize conflict risks).
 
Use translations in front-end code
 
Before using a string in front-end, you need to declare a new constant in `client/@types/global.d.ts`. The constant name must:
 
start with the prefix "LOC_"
 
use the string key, upper cased
 
you just have to declare its type, not its value
 
For example, to use "use_chat", you have to declare:
 
declare const LOC_USE_CHAT: string
 
The `build-client.js` script will read the `client/@types/global.d.ts`, search for such constants, and load their values from the languages files.
 
Now, you can simply call `peertubeHelpers.translate(LOC_USE_CHAT)` in your code.
 
Use translations in back-end code
 
In theory, the only parts of the backend code where you need localization is the settings declaration and standardized data (ActivityPub, RSS, ...). Here we need to get english strings from the translation key.
 
Note: you should never need another language translation from backend code. Localization must be done on front-end.
 
There is a `lib/loc.ts` module providing a `loc()` function. Just pass it the key to have the english string: `loc('diagnostic')`'.
 
Documentation translation
 
The documentation translation is done using the corresponding Weblate component.
 
There is a specific "Hugo shortcodes" you can use to display an application string. Saying you want to display the name of the button "open_chat_new_window", you can use this in the documentation markdown file:
 

Chargement…

Avatar de l’utilisateur Aucun

Chaîne mise à jour dans le dépôt
Use translations in front-end code
 
Il y a un an
Parcourir toutes les modifications de chaînes

Glossaire

Anglais Persan
Aucune chaîne correspondante n’a été trouvée dans le glossaire.

Informations sur la chaîne

Description de la chaîne source
type: Title ###
Drapeaux
no-wrap
Emplacement de la chaîne source
support/documentation/content/en/contributing/translate/_index.md
Âge de la chaîne
Il y a un an
Date de dernière mise à jour
Il y a un mois
Âge de la chaîne source
Il y a un an
Fichier de traduction
support/documentation/po/livechat.fa.po, chaîne 133