I may be wrong, but I *think* such double-replacements are common amongst L10n systems, which is part of why the L10n workflow needs to account for potential security vulnerabilities introduced through the localization process.

One thing that might help in the specific case of the "need to reconnect" localization, though, may be to encapsulate that whole hyperlink in a pre-escaped variable, e.g. instead of the localization string containing the following:

```
(<a href='{{badge.attributes.body.badge.issuer.origin|e}}'>{{badge.attributes.body.badge.issuer.name|e}}</a>)
```

it could just contain `({{linkToIssuer}})`, a pre-escaped value we could inject into the context. This would make the string much easier (and less confusing) to localize, while also reducing the possibility of errors/vulnerabilities creeping into localizations.