2. PeerTube LiveChat
3. Peertube Plugin Livechat Documentation
4. Espagnol
5. Zen

123 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Title ## ConverseJS translations
	Espagnol ↹ ↵ NBS … « » “ ” ﹙-﹚ ‐ – — Traducciones de ConverseJS 26/230 · 23 À vérifier
124 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Plain text 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).
	Espagnol ↹ ↵ NBS … « » “ ” ﹙-﹚ ‐ – — Este plugin se basa en [ConverseJS](https://conversejs.org/) para el front-end del chat. ConverseJS genera sus propias traducciones, en su [instancia weblate](https://hosted.weblate.org/projects/conversejs/#languages). También puedes traducir directamente en el repositorio de código. Para más información, consulta la [documentación sobre las traducciones de ConverseJS](https://conversejs.org/docs/html/translations.html). 427/3900 · 390 À vérifier
125 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Title ## Adding a new locale
	Espagnol ↹ ↵ NBS … « » “ ” ﹙-﹚ ‐ – — Agregar una nueva configuración regional 40/190 · 19 À vérifier
126 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Plain text 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.
	Espagnol ↹ ↵ NBS … « » “ ” ﹙-﹚ ‐ – — Si crees que falta una configuración regional, verifica primero si se toma en cuenta en Peertube. Si es así, puedes [abrir un issue](https://github.com/JohnXLivingston/peertube-plugin-livechat/issues) para solicitarla. 218/2030 · 203 À vérifier
127 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Title ## Adding new strings / use translations in the code
	Espagnol ↹ ↵ NBS … « » “ ” ﹙-﹚ ‐ – — 0/490 · 49 À vérifier
128 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Plain text 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.
	Espagnol ↹ ↵ NBS … « » “ ” ﹙-﹚ ‐ – — 0/1480 · 148 À vérifier
129 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Plain text Each string is linked to a key (for example `use_chat`). Choose an explicit key in english, lower case.
	Espagnol ↹ ↵ NBS … « » “ ” ﹙-﹚ ‐ – — 0/1040 · 104 À vérifier
130 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Plain text 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).
	Espagnol ↹ ↵ NBS … « » “ ” ﹙-﹚ ‐ – — 0/1720 · 172 À vérifier
131 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Title ### Use translations in front-end code
	Espagnol ↹ ↵ NBS … « » “ ” ﹙-﹚ ‐ – — 0/340 · 34 À vérifier
132 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Plain text Before using a string in front-end, you need to declare a new constant in `client/@types/global.d.ts`. The constant name must:
	Espagnol ↹ ↵ NBS … « » “ ” ﹙-﹚ ‐ – — 0/1270 · 127 À vérifier
133 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Bullet: '* ' start with the prefix "LOC_"
	Espagnol ↹ ↵ NBS … « » “ ” ﹙-﹚ ‐ – — 0/280 · 28 À vérifier
134 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Bullet: '* ' use the string key, upper cased
	Espagnol ↹ ↵ NBS … « » “ ” ﹙-﹚ ‐ – — 0/310 · 31 À vérifier
135 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Bullet: '* ' you just have to declare its type, not its value
	Espagnol ↹ ↵ NBS … « » “ ” ﹙-﹚ ‐ – — 0/480 · 48 À vérifier
136 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Plain text For example, to use "use_chat", you have to declare:
	Espagnol ↹ ↵ NBS … « » “ ” ﹙-﹚ ‐ – — 0/520 · 52 À vérifier
137 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Fenced code block (typescript) declare const LOC_USE_CHAT: string
	Espagnol ↹ ↵ NBS … « » “ ” ﹙-﹚ ‐ – — 0/350 · 35 À vérifier
138 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Plain text 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.
	Espagnol ↹ ↵ NBS … « » “ ” ﹙-﹚ ‐ – — 0/1460 · 146 À vérifier
139 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Plain text Now, you can simply call `peertubeHelpers.translate(LOC_USE_CHAT)` in your code.
	Espagnol ↹ ↵ NBS … « » “ ” ﹙-﹚ ‐ – — 0/800 · 80 À vérifier
140 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Title ### Use translations in back-end code
	Espagnol ↹ ↵ NBS … « » “ ” ﹙-﹚ ‐ – — 0/330 · 33 À vérifier
141 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Plain text 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.
	Espagnol ↹ ↵ NBS … « » “ ” ﹙-﹚ ‐ – — 0/2110 · 211 À vérifier
142 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Plain text Note: you should never need another language translation from backend code. Localization must be done on front-end.
	Espagnol ↹ ↵ NBS … « » “ ” ﹙-﹚ ‐ – — 0/1160 · 116 À vérifier