In theory, theonly parts of the backend code where you need localization isthe settings declaration and standardized data (ActivityPub, RSS, ...).Here we need to get english strings from the translation key.
There is a specific "Hugo shortcodes" youcan use to display an application string.Saying you want to display the name of the button "open_chat_new_window", youcan use this in the documentation markdown file:
If a string contains a link, youcan change it for the correct link in the translated language.For example, for a link to this documentation, youcan add the language code in the url.
The tool I use to handle translations for the documentation can have strange behaviours. When I add sentences that looks like other existing sentences, it sometimes copies existing translations. So, when you have translations marked as "to check", please make sure it doesn't copy a string that has nothing to do withthe english one before validating.