I’m having an issue with translating a website where some strings contain dynamic values and HTML formatting. The normal text translates correctly, but after switching to another language, some parts of the page either disappear or the formatting gets messed up. The original English version looks fine. For example, a string might contain something like a placeholder, a link, or a small HTML tag inside the sentence. I’m not sure if I’m handling these correctly in the source file or if there’s a Crowdin setting I’m missing. Has anyone run into something similar? How do you normally handle placeholders and inline HTML when localizing a website with Crowdin?
Hello @islabrownn!
Yes, this can happen when a string contains placeholders or HTML formatting. In general, I’d recommend treating those elements as part of the code rather than something that should be translated.
A few things to check:
-
Make sure placeholders such as
{name},%s, or{{value}}stay exactly the same in the translation. -
Make sure HTML tags such as
<a>,<strong>, or<span>are not removed or changed. -
Check Crowdin’s QA warnings for missing placeholders or mismatched tags.
-
Keep HTML in the source strings as simple as possible.
-
If possible, use Crowdin’s tag/placeholder handling so translators can focus only on the text.
If the English version works but the translated version breaks, the first thing I would check is whether a placeholder or HTML tag was accidentally changed or removed during translation.
If you have a specific example, sharing the source string and its translation would make it easier to spot the issue. You can do that by emailing us at suppor@crowdin.com.