When dealing with tags Translate5 stores them in internal format.
When Translate5 communicates with 3rd party system like t5memory or OpenAI it converts internal tags format to the format understandable by that system. Moreover 3rd party system can return result with malformed (wrong order etc.) or missing tags.
There are several ways how Translate5 deals with tags conversion for communicating with 3rd party systems.
There are configs for each resource that support processing tags. Configs are prefixed with runtimeOptions.LanguageResources then goes system name and then tagHandler. Currently the following configs exist
runtimeOptions.LanguageResources.translate24.tagHandler
runtimeOptions.LanguageResources.deepl.tagHandler
runtimeOptions.LanguageResources.google.tagHandler
runtimeOptions.LanguageResources.groupshare.tagHandler
runtimeOptions.LanguageResources.microsoft.tagHandler
runtimeOptions.LanguageResources.openai.tagHandler
runtimeOptions.LanguageResources.pangeamt.tagHandler
runtimeOptions.LanguageResources.t5memory.tagHandler - system level, not available to be edited in UI
runtimeOptions.LanguageResources.textshuttle.tagHandler
runtimeOptions.LanguageResources.tildemt.tagHandler
Remover is a tag handler which purpose is to remove tags from the text completely so the plain text is sent to the corresponding 3rd party system.
Html image is a tag handler that converts internal tags to html IMG tags.
XLF repair is a tag handler that converts internal tags to XML tags (bx, ex, x etc.).
Tag handler tjat acts similar to the xlf_repair, but specific to the t5memory.
All tag handlers (except remover) are doing tag repair if corresponding system returns result with malformed tags (wrong order, wrong nesting) or missing tags by trying to place appropriate tag on it's expected position if it is possible.