There might be some very technical strings. If you are not 100% sure of the meaning, or of your translation, you better not translate it, so it will display in english.
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).
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.
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).
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.