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.” The fact that some translators decided years ago that it doesn’t fit small hobby forums - where “staff” implies paid employees - and therefore chose “Team” is something no AI will guess, because it’s simply not the correct translation. This is exactly where the Crowdin glossary would help: without it, AI-generated terms will never match what admins actually see in the interface - not because AI can’t translate, but because it doesn’t make the same localization decisions human translators made. It’s the difference between translation and localization.
And that’s similar with other terms like “bootstrap mode” or “impersonation”.
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.