Ask machine translation to handle the same product term twice, and there's no guarantee it comes back the same way. Multiply that across a documentation set, and one button ends up with three different names in three different languages.
We sat down with Alconost to talk through where this actually comes from — and why the fix isn't a smarter MT engine. It's a maintained termbase with an owner, real review, and a process that keeps up when the product changes.
Real incidents included: a core product term that came back as a compound word that doesn't exist in the target language, and a single bad string that spread through a translation memory badly enough to break a client's build.
👉 Full story
1August 19, 2026 144 1
