2. PeerTube LiveChat
3. Croate
4. Zen

prosody_components_description
	Anglais Enable the use of external XMPP components.<br> This option alone only allows connections from localhost. You have to setup the listening interfaces and open the port on your firewall to make it available from remote servers.<br> This feature can, for example, be used to connect some bots to the chatting rooms.
	Croate ↹ ↵ NBS … „ “ ‚ ‘ ﹙-﹚ ‐ – — 0/3130 · 313 À 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:
	Croate ↹ ↵ NBS … „ “ ‚ ‘ ﹙-﹚ ‐ – — 0/1270 · 127 À vérifier
135 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Bullet: '* ' start with the prefix "LOC_"
	Croate ↹ ↵ NBS … „ “ ‚ ‘ ﹙-﹚ ‐ – — 0/280 · 28 À vérifier
prosody_components_port_description
	Anglais The port that will be used by XMPP components to connect to the Prosody server.<br> Change it if this port is already in use on your server.<br> You can keep this port closed on your firewall if you don't allow access on interfaces other than localhost.
	Croate ↹ ↵ NBS … „ “ ‚ ‘ ﹙-﹚ ‐ – — 0/2540 · 254 À vérifier
136 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Bullet: '* ' use the string key, upper cased
	Croate ↹ ↵ 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
	Croate ↹ ↵ 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:
	Croate ↹ ↵ NBS … „ “ ‚ ‘ ﹙-﹚ ‐ – — 0/520 · 52 À vérifier
prosody_components_interfaces_description
	Anglais The network interfaces to listen on for external components connections.<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>172.18.0.42</li> </ul>
	Croate ↹ ↵ NBS … „ “ ‚ ‘ ﹙-﹚ ‐ – — 0/3250 · 325 À vérifier
139 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Fenced code block (typescript) declare const LOC_USE_CHAT: string
	Croate ↹ ↵ NBS … „ “ ‚ ‘ ﹙-﹚ ‐ – — 0/350 · 35 À vérifier
prosody_components_list_description
	Anglais The external components to declare: <ul> <li>One per line.</li> <li>Use the format «component_name:component_secret» (spaces will be trimmed).</li> <li>You can add comments: everything after the # character will be stripped off, and empty lines ignored.</li> <li>The name can only contain latin alphanumeric characters and dots.</li> <li> If the name contains only alphanumeric characters, it will be suffixed with the XMPP domain. For example, «bridge» will become «bridge.your_domain.tld». You can also specify a full domain name, but you have to make sure to configure your DNS correctly. </li> <li>Only use alphanumeric characters in the secret passphrase (use at least 15 characters).</li> </ul>
	Croate ↹ ↵ NBS … „ “ ‚ ‘ ﹙-﹚ ‐ – — 0/7270 · 727 À 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.
	Croate ↹ ↵ 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.
	Croate ↹ ↵ NBS … „ “ ‚ ‘ ﹙-﹚ ‐ – — 0/800 · 80 À vérifier
142 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Title ### Use translations in back-end code
	Croate ↹ ↵ 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.
	Croate ↹ ↵ 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.
	Croate ↹ ↵ 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')`'.
	Croate ↹ ↵ NBS … „ “ ‚ ‘ ﹙-﹚ ‐ – — 0/1320 · 132 À vérifier
146 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Title ## Documentation translation
	Croate ↹ ↵ NBS … „ “ ‚ ‘ ﹙-﹚ ‐ – — 0/250 · 25 À 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.
	Croate ↹ ↵ NBS … „ “ ‚ ‘ ﹙-﹚ ‐ – — 0/800 · 80 À vérifier
148 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Plain text 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:
	Croate ↹ ↵ NBS … „ “ ‚ ‘ ﹙-﹚ ‐ – — 0/2110 · 211 À vérifier
150 support/documentation/content/en/contributing/translate/_index.md
	Anglais type: Plain text You can also prevent a whole page from being translating by adding `livechatnotranslation: true` in the Yaml Font Matter section:
	Croate ↹ ↵ NBS … „ “ ‚ ‘ ﹙-﹚ ‐ – — 0/1290 · 129 À vérifier