nat
March 31, 2026, 9:55am
8
Adding the PR here as well:
main ← ai-translation-category-pm
merged 02:53PM - 31 Mar 26 UTC
Related: https://meta.discourse.org/t/feature-request-limit-topic-translation-to… -specific-categories/392993
The old `ai_translation_backfill_limit_to_public_content` setting was too coarse. It either translated everything or only public content, with no way to pick specific categories or control PM translation separately.
This replaces it with two settings:
- `ai_translation_target_categories` (category_list): pick exactly which categories get translated. Subcategories need to be added separately. Empty means no category topics get translated.
- `ai_translation_private_messages` (enum: none / group / all): controls PM translation independently. none disables it, group limits to group PMs, all includes ... all.
Tags are switched to "always translated".
The migration reads the old setting and maps it to the new settings, so existing sites keep their current behaviour. It also cleans up the old setting.
<img width="359" height="511" alt="Screenshot 2026-03-31 at 5 33 45 PM" src="https://github.com/user-attachments/assets/48ed19e8-f559-447c-a7af-c235698d62df" />
Settings will be migrated if ai_translation_enabled or ai_translation_backfill_limit_to_public_content have been modified to non-default values. Untouched otherwise.
ai_translation_backfill_limit_to_public_content = true will now be
ai_translation_target_categories = <all public categories>ai_translation_personal_messages = none
Conversely, if ai_translation_backfill_limit_to_public_content = false, it will now be
ai_translation_target_categories = <all categories>ai_translation_personal_messages = all
ai_translation_personal_messages also allows a group setting.
3 Likes