2. PeerTube LiveChat
3. Espagnol
4. Zen

129 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
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.
	Espagnol ↹ ↵ NBS … « » “ ” ﹙-﹚ ‐ – — 0/1480 · 148 À 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.
	Espagnol ↹ ↵ NBS … « » “ ” ﹙-﹚ ‐ – — 0/1040 · 104 À vérifier
prosody_c2s_interfaces_label
	Anglais Client to server network interfaces
	Espagnol ↹ ↵ NBS … « » “ ” ﹙-﹚ ‐ – — 0/350 · 35 À 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).
	Espagnol ↹ ↵ NBS … « » “ ” ﹙-﹚ ‐ – — 0/1720 · 172 À vérifier
prosody_c2s_interfaces_description
	Anglais The network interfaces to listen on for client to server connections.<br> This setting is provided for advanced users. Don't change this setting if you don't fully understand what it means.<br> List of IP to listen on, coma separated (spaces will be stripped).<br> You can use «*» to listen on all IPv4 interfaces, and «::» for all IPv6.<br> Examples: <ul> <li>*, ::</li> <li>*</li> <li>127.0.0.1, ::1</li> <li>127.0.0.1, ::1, 172.18.0.42</li> </ul>
	Espagnol ↹ ↵ NBS … « » “ ” ﹙-﹚ ‐ – — 0/4580 · 458 À vérifier
133 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Title ### Use translations in front-end code
	Espagnol ↹ ↵ NBS … « » “ ” ﹙-﹚ ‐ – — 0/340 · 34 À 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:
	Espagnol ↹ ↵ NBS … « » “ ” ﹙-﹚ ‐ – — 0/1270 · 127 À vérifier
135 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Bullet: '* ' start with the prefix "LOC_"
	Espagnol ↹ ↵ NBS … « » “ ” ﹙-﹚ ‐ – — 0/280 · 28 À vérifier
136 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Bullet: '* ' use the string key, upper cased
	Espagnol ↹ ↵ NBS … « » “ ” ﹙-﹚ ‐ – — 0/310 · 31 À vérifier
137 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
138 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
139 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
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.
	Espagnol ↹ ↵ NBS … « » “ ” ﹙-﹚ ‐ – — 0/1460 · 146 À 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.
	Espagnol ↹ ↵ NBS … « » “ ” ﹙-﹚ ‐ – — 0/800 · 80 À vérifier
142 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Title ### Use translations in back-end code
	Espagnol ↹ ↵ NBS … « » “ ” ﹙-﹚ ‐ – — 0/330 · 33 À 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.
	Espagnol ↹ ↵ NBS … « » “ ” ﹙-﹚ ‐ – — 0/2110 · 211 À 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.
	Espagnol ↹ ↵ NBS … « » “ ” ﹙-﹚ ‐ – — 0/1160 · 116 À 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')`'.
	Espagnol ↹ ↵ NBS … « » “ ” ﹙-﹚ ‐ – — 0/1320 · 132 À vérifier
146 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Title ## Documentation translation
	Espagnol ↹ ↵ NBS … « » “ ” ﹙-﹚ ‐ – — 0/250 · 25 À vérifier