our use case: We are German forum, but we have EN-speaking advertising clients. Hence it would be great to be able to limit topic localizations to specific categories only.
A follow-up on this feature. We made a technical change recently
Following that change, the ability to limit topic translation to specific categories is still present. But unlike the initial implementation, now Discourse defaults to translating all content and an ai_translation_excluded_categories site setting is available to do just that, exclude categories from translation.
Existing communities should have been migrated automatically to this system. Let us know if you run into any issues.
Makes sense for forums that want most things translated. I want to float the inverse case as an RFC and gauge how common it actually is:
Iād like to translate only one busy multilingual category (e.g. āInternationalā) and leave the rest of the forum alone. With exclude-only that means listing every other category, and every new category I add later gets translated by default until I remember to exclude it an easy way to pay for translations I never wanted. An opt-in ai_translation_target_categories (include wins if set, else translate-all-minus-excludes) would fit this cleanly and is safer for cost control.
How common is this scenario for others? Do you want translation forum-wide, or scoped to a single international/off-topic category? Trying to gauge whether an allow-list is worth bringing back or if my setup is the niche one ..
Appreciate the question. I am curious to see as well if this is a common use case.
My gut feeling is that most communities benefit immensely from translating all public content. Users in other languages (often, non-English speakers) will see all content in their language, itās a much nicer experience. There is a cost, of course, but itās not very high. On our hosting, itās free for most communities.