I translated a post, manually, to Spanish and Portuguese (BR). [image] Even if I change my website to `pt` or `en`, it still shows the content in its original language. Both on my account and outside it. ?tl=es and ?tl=pt_BR doesn’t seem to work, either. I have everything setup. [image] Edit 1: This is the post: The best ideas of Blokoto, drawn by the community! - News - Blokoto Community Edit 2: Locale is null on the response. Even in a link with the tl param. The best ideas of Blokoto, drawn by the community! - News - Blokoto Community [image]

When you edit the post, is the locale it was written in selected? It should look like this [Screenshot_20260711_074544_Firefox] I think if that is blank, showing translations doesn’t work. So if it looks like this - without a language, try to select the language [Screenshot_20260711_074608_Firefox]

It is working now, thanks for the help!

I recently struggled with this too. I think something needs to be improved, for example, that you need to select the language of the original when you add the first translation. I think currently there is a problem with permissions. You can configure that users can help with translations, but those users cannot edit the original to select the language. As long as AI handles the language detection this isn’t that much of a problem - users only need it in cases where that is wrong, but without AI the author of the post needs to remember to select a language or a user with edit all posts permission needs to select it for them.

Indeed. I was thinking my instance was broken because of this. I think the translations should override the content even if the main content is not set with a locale, that would be the expected behavior

[图片] paulovbettio: I think the translations should override the content even if the main content is not set with a locale We’ve thought of the issue before - the problem with doing this is that if the post is in English but not set, and a user puts an “en” translation, the translation should be shown instead of the original post in English.

I’m adding a bit of an improvement here: UX: Allow user to set post and topic title language when manually creating post translations in modal (#41734) main ← manual-407319 merged 02:43AM - 16 Jul 26 UTC (UTC) [图片] nattsw +770 -24 Related: https://meta.discourse.org/t/manual-localization-doesnt-seem-to-be-work…ing/407319 Users have gotten tripped over and over again when manually inserting translations for posts, not knowing they need to set the post language first before the translation is shown (explained [here](https://meta.discourse.org/t/manual-localization-doesnt-seem-to-be-working/407319/7?u=nat)). This PR adds the ability to allow the user to set the post language in the modal when they are working with translations, highlighting the fact that they need to set the post language before translations can be shown | before | after | |---|---| | | We’ll indicate that you’ll need to set the post language so that translations can show up. Here’s a screenshot from the PR: [image] This area matches where you (OP) looked up when the translations weren’t showing up, so hopefully this will help highlight this gotcha moving on. It’s just merged, so give it some time for the new image to be built.

手动本地化似乎不起作用

产品支持

Moin 2026 年7 月 11 日 05:48 2

编辑帖子时，是否选择了其原始语言？

它应该看起来像这样

我认为如果那里是空的，就无法显示翻译。所以如果它看起来像这样——没有选择语言，请尝试选择一种语言

话题		回复	浏览量
Post not being detected as German Product Support ai , content-localization	14	676	2026 年4 月 16 日
Falsche Übersetzung, wenn post locale = UI locale Bug ai , dynaloc , content-localization	2	261	2026 年8 月 24 日
AI Translation skips Portuguese (pt) locale - post translated to all languages except Portuguese Bug ai , dynaloc	25	896	2026 年4 月 22 日
Content Localization - Manual and Automatic with Discourse AI Site Management ai , content-localization	54	6224	2026 年8 月 7 日
Quoting with content localization selects the language the user sees Bug content-localization	2	171	2025 年9 月 1 日

手动本地化似乎不起作用

相关话题