We have quite a few messages which include <a href="https://...">some phrase</a> content. The target URLs and HTML markup are unwelcome noise for the translators to deal with. It would be nice to find a usable system that separates presentation, configuration, and content so that only the content is left in the message files for the translators to deal with.
The various parts could be kept in the i18n source files as separate messages with the invariant messages being marked as such in the qqq.json file. The application's view tier would need some sort of update however to know which set of messages to load and combine in order to render the desired message.