# Solicitud de función: Limitar la traducción de temas a categorías específicas
**URL:** https://meta.discourse.org/t/feature-request-limit-topic-translation-to-specific-categories/392993
**Category:** Feature
**Tags:** content-localization
**Created:** [8 Enero, 2026 17:44 UTC](https://meta.discourse.org/t/feature-request-limit-topic-translation-to-specific-categories/392993 "2026-01-08T17:44:31Z")
**Posts on this page:** 1
**Showing post:** 5
### Author:  [@nat](https://meta.discourse.org/u/nat)
#### Post date: [31 Marzo, 2026 09:48 UTC](https://meta.discourse.org/t/feature-request-limit-topic-translation-to-specific-categories/392993/5 "2026-03-31T09:48:49Z")
Añadimos esto por ahora:
>
>
> 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.
>
> \
Danos uno o dos días para fusionarlo.
---
_[View the full topic](https://meta.discourse.org/t/feature-request-limit-topic-translation-to-specific-categories/392993)._