Локализация контента и автоматический перевод для вашего сообщества

[nat (Natalie T)]

Локализация контента и автоматический перевод теперь готовы, обеспечивая многоязычную поддержку для ваших сообществ. Эта функция включена здесь, на Meta.

Наши эксперименты здесь вызвали огромный интерес, пока мы занимались доработками, и мы рады сообщить, что ожидание наконец закончилось: теперь вы можете использовать эти замечательные новые функции на своих сайтах.

Благодаря этим мощным нововведениям вы теперь можете переводить и предоставлять контент вашего сайта на нескольких языках для создания бесшовного многоязычного опыта. От заголовков тем до содержимого постов, а также категорий и их описаний — ваше сообщество теперь может быть полностью переведено на множество языков по вашему выбору.

Подробности о функции и инструкции по настройке вы найдете в теме документации: Content Localization - Manual and Automatic with Discourse AI

Размещено нами? Эта функция доступна во всех наших тарифных планах с хостингом.

Часто задаваемые вопросы (FAQ)

Какой LLM использует Meta (этот форум)?
Мы проводили итерации и пока остановились на Gemini Flash 2.5; еще несколько недель назад мы использовали версию 2.0. Поддержка языков и стоимость будут продолжать меняться, и мы ожидаем обновлять модель по мере нахождения более подходящих вариантов. Этот рейтинг от OpenRouter полезен для определения того, что обычно используется: LLM Rankings | OpenRouter.

Но… сколько это всё стоит?
Стоимость перевода вашего сообщества зависит от множества переменных: выбранная модель, размер постов, количество тем, количество категорий. Мы рекомендуем установить приемлемую дневную квоту, а затем корректировать её по мере необходимости. Discourse AI - AI usage и Configuring LLM Usage Quotas in Discourse AI — отличные темы по мониторингу использования.

В качестве очень приблизительной оценки: перевод 🇨🇳 Discourse supports Chinese usernames | Discourse 支持中文用户名 на 2 языка (английский и японский) с использованием профиля по умолчанию занимает 7800 токенов. При использовании Gemini 2.5 Flash Lite это стоит $0.001030.

Грядущие функции и улучшения

Предоставление локализованного контента для SEO

Мы хотим помочь публичным сообществам привлекать больше органического трафика. Если ваш сайт определяет набор поддерживаемых локалей, каждая тема будет также содержать ссылки на свои переведенные версии для индексации поисковыми системами, такими как Google.

Выполнено

Выборщики локалей, понятные вам

В настоящее время на уровне всего сайта в выпадающем списке для японского языка указано «日本語». Мы должны использовать «Japanese», когда интерфейс отображается на английском языке.

Выполнено

Локализация тегов

В текущем виде теги не так надежны, как категории, и имеют некоторые особенности. Для добавления функций локализации теги потребуют фундаментальных изменений. ^[1]

Выполнено

Повторный перевод отредактированных постов

В настоящее время переведенный пост не переписывается заново, когда оригинал редактируется. Мы рассматриваем внедрение хороших пороговых значений по умолчанию или предоставление определенных элементов управления, которые позволят привилегированным пользователям запускать автоматический перевод отредактированного поста.

Выполнено

Дашборд прогресса перевода сообщества

Владельцам сообществ бывает сложно увидеть, какая часть их форума уже локализована.

Наша цель — показать дашборд, отображающий прогресс перевода для каждого настроенного языка.

Выполнено

Oneboxes и ссылки

В настоящее время они не отображаются корректно в локализованных темах. Это будет исправлено.

Выполнено

Есть вопрос или предложение?

Если вы обнаружили область, которая не была локализована, хотя должна была быть, или хотели бы предложить улучшения, мы с радостью выслушаем вас и обсудим ваши предложения внутри команды.

Пожалуйста, добавьте их в эту тему, и мы выделим их в отдельные темы, если это потребуется.

---

1. Сравнение категории Bug - Discourse Meta и тега Topics tagged email дает нам понять, что теги идентифицируются не по их ID, а по именам. ↩︎

[Simon_Manning]

@nat

Currently sitewide, we have “日本語” for Japanese in the dropdown selector. We should use “Japanese” instead when viewing it in English.

I’m curious about the rationale behind this part. If I am a native English reader viewing in English, the language drop-down (typically) has no relevance to me while if my native language is different (still viewing in English), what I think would make sense to me is to see the name of my language in my native script.

[nat (Natalie T)]

We did have an internal conversation about this – here’s an example on why it might make sense:

Some language pickers include the language in both the localized and original text, e.g.

• Japanese 日本語
• Arabic اللغة العربية

So that’s what we’re considering.

[Simon_Manning]

Thanks, the search issue makes a lot of sense and changing those titles is a far less complex and wide reaching change than allowing alternative search terms for the values.

I like the idea of using both English (whatever language I am running in?) and the native script, since it won’t potentially negatively impact native other-language readers.

[Moin]

When a user flags a post do moderators see in which language the user read it?

So for example if I flagged this post as off topic

@donaldsoncd

Heathrow geschlossen: Flugausfälle werden voraussichtlich noch Tage andauern, sagt der Manager des Flughafens von London

would you know that I saw a weird translation and the flag is not related to the original content?

[nat (Natalie T)]

@Moin

do moderators see in which language the user read it?

Currently no, but good point. It could make sense to create a new custom flag to do so.

EDIT: Done.

[Moin]

The flag is definitely helpful. But it requires that I compare the original post and the translation I see.
When I don’t do that, an indicator that I was looking at the German version when I flagged as off-topic would still be helpful. Especially in cases where the original isn’t in English, so I cannot tell without research if the translation or the original is the problem.

Does the custom flag affect trust levels? It would be unfair to punish users for mistakes in translations they didn’t write.

Edit:

@nat

EDIT: Done.

I tried it right away

[nat (Natalie T)]

I see, I believe I misinterpreted you. But regardless the flag is there to flag incorrect translations.

I now understand your original intent and that’s a good point as well. Coincidentally, there’s a review queue revamp going on right now - Current Projects - April 2025. I’ll collaborate with that team to see if we can add some metadata to the moderator viewing the flagged post. As usual, thank you for your sharp observation.

@Moin

Does the custom flag affect trust levels? It would be unfair to punish users for mistakes in translations they didn’t write.

From what I can read, no - agreeing with a custom flag does not penalize the user.

[asa]

Thank you very much useful.

Just a quick question does the translation plugin need to be activated?

[nat (Natalie T)]

@asa

does the translation plugin need to be activated?

Nope, good question - the translator plugin is not used at all. I would recommend to disable it to prevent confusion.

[asa]

What are the implications for SEO when utilizing this feature? Could it potentially lead to adverse effects?

[nat (Natalie T)]

@asa

What are the implications for SEO when utilizing this feature

The feature to serve translated content has not been implemented yet.

But to address the question properly – our team has had discussions about this before and I honestly don’t think we need to worry about adverse effects. In fact our feature would actually improve international site traffic if we’re talking about Google specifically.

Using Reddit as an example today, let’s say you’re a Spanish reader searching for espresso machines on reddit:

Search result for ‘espresso machines reddit’ - see the URL

The first result is a machine-translated post on reddit, its URL being https://www.reddit.com/r/espresso/comments/1fbwbun/most_vfm_entry_espresso_machine/?tl=es-es (note the tl language query parameter). As most reddit users will know, searching for content in their language may now lead to seeing machine translations done by the Google API themselves (Reddit and Google have a huge collab). These folks did some research as well and I trust their content – AI-Generated Content Does Not Hurt Your Google Rankings (600,000 Pages Analyzed).

So, Google is taking your original content and machine-translating it themselves, potentially taking traffic away from your site. The blog post from the same folks here (Google Is Stealing Your International Search Traffic With Automated Translations) does a good walkthrough on how this might be happening, and makes the recommendation that you should translate your content yourself. With the localization feature we have, you can start localizing your content (whether through AI or manually), with the added benefit of ensuring your translated topics are at a quality you desire.

[asa]

Thanks that’s a good example with Reddit, I did some more research Reddit also seems to use hreflang flags is it planned in this way too?

Reddit AI translations have been scaling across languages and Google rankings...

[nat (Natalie T)]

@asa

hreflang

Yup, that’s the way it will be.

It won’t be a rapid rollout as we have to do some tests first as well.

[eisammy (Sammy)]

If i want writte my reply with my native lang I could? because a couple months ago I tried and I was warned, translate my content means that my internacional traffic it’s allowed typing in any language right?

Look your example: I still using Reddit even as Lurker and this translate has been translating to me native lang til ours ways to says, example? When I say ‘Hello’ in english here we not says ‘Olá’ but ‘Fala tu’ and Reddit today understand this, you’ve sure that this model will learn translate this way with 7.800 tokens?

For last, any chances to CDCK provide an API paid to translate our communities I did this question in the past but now that apparentely there a team for that i’m here again

[maiki]

This is so rad!

---

@Simon_Manning

@nat

Currently sitewide, we have “日本語” for Japanese in the dropdown selector. We should use “Japanese” instead when viewing it in English.

I’m curious about the rationale behind this part.

I was also surprised by this! My background is in public surveying for multilingual constituencies, and it was sometimes a challenge to explain to some stakeholders why the multilingual menu options made sense to readers, rather than English visitors.

It is kind of a wild time for multilingual systems, with LLMs producing reliable results! And I’m looking forward to learning new patterns to apply so we can talk to the most people.

---

@nat

@asa

does the translation plugin need to be activated?

Nope, good question - the translator plugin is not used at all. I would recommend to disable it to prevent confusion.

So this is just the Discourse AI plugin?!

I’m going to need to rethink a few things, but I think I can just switch over to Discourse AI translations with minimal fuss.

[nat (Natalie T)]

@eisammy

If i want writte my reply with my native lang I could

Yes, that is the case. The whole topic can be written natively in 20 languages and will be served in German to a German reader, if the supported languages include German.

@eisammy

When I say ‘Hello’ in english here we not says ‘Olá’ but ‘Fala tu’ and Reddit today understand this, you’ve sure that this model will learn translate this way with 7.800 tokens?

Discourse will not provide recommendations on which model you should use, so you should choose a model which supports translating to the languages of your choise.

Mentioned in docs is also the ability to customize the persona that includes the prompt and model.

@nat

• AI translation post raw translator persona (and other personas) - In more formal communities, admins may choose to create their own persona. This allows you to set a prompt that is more fine-tuned to the language or vocabulary you prefer.

You can refer to AI bot - Personas on how to configure suitable personas and fine-tune prompts for each function.

---

@eisammy

For last, any chances to CDCK provide an API paid to translate our communities I did this question in the past but now that apparentely there a team for that i’m here again

I don’t really understand what you mean here, can you elaborate or share what this question is?

Not sure if this is what you mean, but CDCK will unlikely provide any other paid services, however - A customer on our hosting may set up this feature with the CDCK-hosted models but there are language limits based on which tier they are on.

[David_Ghost]

I have a forum in Portuguese language. Some time ago, I was thinking about creating another forum in the same niche as the one I currently have, but in french, my second language. But I gave up because it would be too much work to create content for two new forums.

I’m very happy about this announcement and look forward to it being implemented.