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

127 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Title ## Adding a new locale
	Arabe ZWNJ ZWJ LRM RLM LRE RLE PDF LRO RLO ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 0/190 · 19 RTL LTR À vérifier
128 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.
	Arabe ZWNJ ZWJ LRM RLM LRE RLE PDF LRO RLO ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 0/2030 · 203 RTL LTR À vérifier
129 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Title ## Adding new strings / use translations in the code
	Arabe ZWNJ ZWJ LRM RLM LRE RLE PDF LRO RLO ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 0/490 · 49 RTL LTR À vérifier
130 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.
	Arabe ZWNJ ZWJ LRM RLM LRE RLE PDF LRO RLO ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 0/1480 · 148 RTL LTR À vérifier
131 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.
	Arabe ZWNJ ZWJ LRM RLM LRE RLE PDF LRO RLO ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 0/1040 · 104 RTL LTR À vérifier
132 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).
	Arabe ZWNJ ZWJ LRM RLM LRE RLE PDF LRO RLO ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 0/1720 · 172 RTL LTR À vérifier
133 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Title ### Use translations in front-end code
	Arabe ZWNJ ZWJ LRM RLM LRE RLE PDF LRO RLO ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 0/340 · 34 RTL LTR À vérifier
134 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:
	Arabe ZWNJ ZWJ LRM RLM LRE RLE PDF LRO RLO ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 0/1270 · 127 RTL LTR À vérifier
135 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Bullet: '* ' start with the prefix "LOC_"
	Arabe ZWNJ ZWJ LRM RLM LRE RLE PDF LRO RLO ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 0/280 · 28 RTL LTR À vérifier
136 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Bullet: '* ' use the string key, upper cased
	Arabe ZWNJ ZWJ LRM RLM LRE RLE PDF LRO RLO ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 0/310 · 31 RTL LTR À vérifier
137 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Bullet: '* ' you just have to declare its type, not its value
	Arabe ZWNJ ZWJ LRM RLM LRE RLE PDF LRO RLO ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 0/480 · 48 RTL LTR À vérifier
138 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Plain text For example, to use "use_chat", you have to declare:
	Arabe ZWNJ ZWJ LRM RLM LRE RLE PDF LRO RLO ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 0/520 · 52 RTL LTR À vérifier
139 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Fenced code block (typescript) declare const LOC_USE_CHAT: string
	Arabe ZWNJ ZWJ LRM RLM LRE RLE PDF LRO RLO ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 0/350 · 35 RTL LTR À vérifier
140 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.
	Arabe ZWNJ ZWJ LRM RLM LRE RLE PDF LRO RLO ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 0/1460 · 146 RTL LTR À vérifier
141 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.
	Arabe ZWNJ ZWJ LRM RLM LRE RLE PDF LRO RLO ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 0/800 · 80 RTL LTR À vérifier
142 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Title ### Use translations in back-end code
	Arabe ZWNJ ZWJ LRM RLM LRE RLE PDF LRO RLO ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 0/330 · 33 RTL LTR À vérifier
143 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.
	Arabe ZWNJ ZWJ LRM RLM LRE RLE PDF LRO RLO ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 0/2110 · 211 RTL LTR À vérifier
144 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.
	Arabe ZWNJ ZWJ LRM RLM LRE RLE PDF LRO RLO ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 0/1160 · 116 RTL LTR À vérifier
145 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Plain text There is a `lib/loc.ts` module providing a `loc()` function. Just pass it the key to have the english string: `loc('diagnostic')`'.
	Arabe ZWNJ ZWJ LRM RLM LRE RLE PDF LRO RLO ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 0/1320 · 132 RTL LTR À vérifier
147 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Plain text The documentation translation is done using the corresponding Weblate component.
	Arabe ZWNJ ZWJ LRM RLM LRE RLE PDF LRO RLO ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 0/800 · 80 RTL LTR À vérifier