You can use the `livechat_label` short code to use application strings.See here: [Documentation translation](/peertube-plugin-livechat/contributing/translate/#documentation-translation).
It is possible to prevent a file from beeing translating, using `livechatnotranslation: true` in the Yaml Font Matter section.See here: [Documentation translation](/peertube-plugin-livechat/contributing/translate/#documentation-translation).
Please use the `livechatnotranslation` option for technical documentation.We don't want technical documentation to be translated, to avoid issues because of a wrong translation.
Try to autodetect colors from user's current theme.<br> When this setting is enabled, the plugin tries to auto-detect colors to apply to the chat theme.<br> If this is not correctly working for some of your Peertube theme, you can disable this option. You can report the bug on the official <a href="https://github.com/JohnXLivingston/peertube-plugin-livechat/issues" target="_blank"> issue tracker </a>. Don't forget to specify which theme is not working.
There may be links to this documentation elsewhere on the web.Try not to change the urls of the documentation pages.Or at the very least, put links to the new location on the previous url.
When a new feature is released, you can use the `livechat_version_notice` short code to display an infobox with the version with which the features is available.This short code takes the version number as parameter.Here is an example:
Warning: don't check this setting if you are not sure of what you are doing.<br> By checking this setting, your Peertube will use the Prosody server that comes with your system, and not the embedded AppImage.<br> Only use this if you encounter problems with the embedded Prosody.