# AI-generated tag translations do not work perfectly

**URL:** https://meta.discourse.org/t/ai-generated-tag-translations-do-not-work-perfectly/399570
**Category:** Site feedback
**Tags:** tags, ai, dynaloc
**Created:** [March 30, 2026, 3:24pm UTC](https://meta.discourse.org/t/ai-generated-tag-translations-do-not-work-perfectly/399570 "2026-03-30T15:24:15Z")
**Posts on this page:** 1
**Showing post:** 9

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [March 30, 2026, 5:48pm UTC](https://meta.discourse.org/t/ai-generated-tag-translations-do-not-work-perfectly/399570/9 "2026-03-30T17:48:51Z")

</div>

> [@Moin](#):
>
> I don’t think any model would choose the same translations for Meta as German translators did for the Discourse interface. “Mitarbeiter” is a perfect translation for “staff.”

It would, as it would have access to that exact same choice on the `config/locales/**/*.yml` files for reference.

> [@Moin](#):
>
> This does not only affect tags, but everything localized here. Whether it’s a guide or a tag, matching the terms users actually see in their interface is more useful than a linguistically perfect translation that doesn’t align with what the software says.

Definitely, and for small enumerable groups, like categories and tags giving the agent access to the existing translations, which are part of the source code would help grounding them.

We can’t do that for the posts, as the cost would be too great, but it is an option for smaller sites or customers with larger translation budgets.

---

_[View the full topic](https://meta.discourse.org/t/ai-generated-tag-translations-do-not-work-perfectly/399570)._