커뮤니티를 위한 콘텐츠 현지화 및 자동 번역

[nat (Natalie T)]

콘텐츠 로컬라이제이션과 자동 번역 기능이 이제 준비되었습니다. 이를 통해 커뮤니티에 다국어 지원이 제공됩니다. 이 기능은 현재 Meta에서 활성화되어 있습니다.

우리가 이 기능에 대해 작업해 온 동안 상당한 관심을 불러일으켰고, 이제 드디어 기대가 끝났으며 여러분의 사이트에서도 이 훌륭한 새 기능을 라이브로 사용할 수 있게 되어 매우 기쁩니다.

이러한 강력한 새로운 추가 기능을 통해 이제 사이트의 콘텐츠를 여러 언어로 번역하여 제공함으로써 매끄러운 다국어 경험을 선사할 수 있습니다. 주제 제목부터 게시물 콘텐츠, 그리고 카테고리 및 그 설명에 이르기까지, 커뮤니티는 이제 여러분이 선택한 다양한 언어로 완전히 번역될 수 있습니다.

기능 세부 사항 및 설정 방법에 대한 자세한 내용은 문서 주제를 방문하세요: Content Localization - Manual and Automatic with Discourse AI

우리가 호스팅을 담당하나요? 이 기능은 저희의 모든 호스팅 플랜에서 사용할 수 있습니다

FAQ

Meta(이 포럼)는 어떤 LLM을 사용하고 있나요?
우리는 반복적으로 개선해 왔으며, 현재는 Gemini Flash 2.5로 정착했습니다. 몇 주 전까지는 2.0을 사용하고 있었습니다. 언어 지원과 비용은 계속 진화할 것이며, 더 나은 옵션을 찾으면 그에 따라 업데이트할 예정입니다. OpenRouter의 이 지표는 일반적으로 어떤 모델이 사용되는지 파악하는 데 유용합니다 - OpenRouter.

그런데 … 이 모든 것이 얼마나 비용이 들까요?
커뮤니티 번역에 드는 비용에는 여러 변수가 있습니다: 선택된 모델, 게시물 크기, 주제 수, 카테고리 수 등. 일일 허용 할당을 설정한 후 진행 상황에 따라 조정하는 것을 권장합니다. Discourse AI - AI usage 와 Configuring LLM Usage Quotas in Discourse AI 는 사용량을 모니터링하는 데 훌륭한 주제입니다.

매우 대략적인 기준으로, 🇨🇳 Discourse supports Chinese usernames | Discourse 支持中文用户名 을 기본 페르소나를 사용하여 2개 언어(영어 및 일본어)로 번역하면 7,800개의 토큰이 사용됩니다. Gemini 2.5 Flash Lite를 사용하면 비용은 $0.001030입니다.

예정된 기능 및 개선 사항

SEO를 위한 로컬라이제이션된 콘텐츠 서빙

공개 커뮤니티가 더 많은 유기적 트래픽을 얻을 수 있도록 돕고 싶습니다. 사이트에서 지원하는 로케일 집합을 정의하면, 모든 주제가 Google과 같은 검색 엔진이 색인화할 수 있도록 번역된 버전으로의 링크를 표시합니다.

완료

여러분에게 의미 있는 로케일 선택기

현재 사이트 전체에서 드롭다운 선택기에 일본어는 “日本語”로 표시됩니다. 영어로 보고 있을 때는 대신 “Japanese”를 사용해야 합니다.

완료

태그 로컬라이제이션

현재 태그는 카테고리만큼 견고하지 않고 몇 가지 특이점이 있습니다. 로컬라이제이션 기능을 추가하기 전에 태그는 근본적으로 몇 가지 변경이 필요합니다. ^[1]

완료

수정된 게시물 재번역

현재 번역된 게시물은 원본이 수정될 때 재번역되지 않습니다. 우리는 몇 가지 좋은 기본 임계값을 고려하거나, 특권 사용자가 수정된 게시물에 대해 자동 번역을 트리거할 수 있도록 특정 컨트롤을 노출하는 것을 고려하고 있습니다.

완료

커뮤니티 번역 진행 상황 대시보드

커뮤니티 소유자로서 포럼의 얼마나 많은 부분이 로컬라이제이션되었는지 쉽게 볼 수 없습니다.

우리는 설정한 언어별 번역 진행 상황을 표시하는 대시보드를 표시하는 것이 의도입니다.

완료

Oneboxes 및 링크

이들은 현재 로컬라이제이션된 주제에서 올바르게 표시되지 않습니다. 이 문제는 수정될 것입니다.

완료

질문이나 제안이 있나요?

로컬라이제이션되어야 하는데 그렇지 않은 영역을 발견했거나, 개선 사항을 제안하고 싶다면, 우리는 기꺼이 경청하고 여러분의 제안을 내부적으로 추가 논의하기 위해 채택할 것입니다.

이 주제에 추가해 주시면, 자체 공간이 필요한 경우 새로운 주제로 분기(fork)할 것입니다.

---

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?
https://www.gsqi.com/marketing-blog/reddit-ai-translations-google/

[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.