Proposal for Korean Translation of webrtc.org

[Seonghoon Baek]

Hello WebRTC Community,

I am a software engineer from South Korea and a big fan of the WebRTC project. The webrtc.org website has been a great resource for my work, and I believe a Korean version would be very helpful for the growing developer community in my country.

I am writing to see if there is an ongoing project to translate webrtc.org into Korean. If there is, I would love to contribute and help in any way I can.

If a translation project has not yet been started, I would like to volunteer to help make it happen. Could you please guide me on the best way to get started and how to collaborate with others?

Thank you for your time and for all your work on this fantastic project.

Best regards,

[Byoungchan Lee]

First of all, webrtc.org — like other Google documentation projects — is already machine-translated. Have you checked?

Also, Google has never shown interest in supporting community-driven translations. Projects like React, Rust, or Python succeeded with i18n docs only because they built their own infrastructure for it. WebRTC has nothing like that, and it’s unrealistic to expect otherwise.

For higher-level usage, Mozilla’s Web API documentation or webrtc.org itself is already enough. Mozilla even has a Korean translation covering typical API usage, though I’ve never relied on it myself.

If you want a deeper understanding, the only dependable approach is reading WebRTC’s C++ source code and the RFCs. Secondary documentation simply won’t cut it.

And here’s the real problem: maintaining translated docs is a huge task, and when they inevitably fall behind, they actively mislead users. Outdated docs are worse than none at all. I’ve seen this firsthand with Android’s Korean docs — they were misleadings that I had to install a browser extension to block them and force English only.

Honestly, the WebRTC community just isn’t large enough to justify the cost of setting up and maintaining proper i18n infrastructure. Combined with Google’s existing machine translation, I don’t see any sustainable path forward.

Since I’m also Korean, I understand the motivation to expand Korean resources in tech, and I’ve seen a few success stories elsewhere. But in the case of WebRTC, I don’t see it happening — not only because it’s a Google project with machine translation already in place, but also because the community simply isn’t big enough to sustain it.

Thanks.

[Sean DuBois]

Have you looked at webrtcforthecurious.com yet? Maybe it covers what you are trying to learn.

No Korean translation yet, but would love one!

On Sep 1, 2025, at 18:14, 'Byoungchan Lee' via discuss-webrtc <discuss...@googlegroups.com> wrote:

First of all, webrtc.org — like other Google documentation projects — is already machine-translated. Have you checked?

Confidential / 대외비

CONFIDENTIALITY NOTICE: This e-mail communication and any attachments contains confidential and privileged information for the sole use of the designated recipients named above. It is prohibited to disclose, disseminate, distribute or copy this e-mail and any attachments beyond the scope which is mutually agreed with the sender of this e-mail. If you are not the intended recipient, please notify the sender by return e-mail and delete and/or destroy all copies of this communication and any attachments immediately.

본 이메일 및 첨부파일은 지정된 수신인만을 위한 것이며, 회사의 비밀정보를 포함합니다. 본 정보를 발신인과 합의된 범위 외에 사용, 공개, 배포하는 것은 엄격히 금지됩니다. 귀하가 만일 지정된 수신인이 아닌 경우, 발신인에게 그 사실을 통지해 주시고 원본 이메일과 첨부파일 및 모든 사본을 즉시 삭제하여 주시기 바랍니다.

--
This list falls under the WebRTC Code of Conduct - https://webrtc.org/support/code-of-conduct.
---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/discuss-webrtc/4748b5f3-810a-42b1-9e10-2b7fd368a898n%40googlegroups.com.

[Seonghoon Baek]

Thank you so much for the suggestion. As a product engineer working with PBX, WebRTC, and AI, I asked because I want to help people in Korea easily understand WebRTC technology. I noticed that the https://webrtc.org website has a language selection dropdown in the top right corner, so I wondered if any help might be needed there.

Thank you so much for introducing me to webrtcforthecurious.com :)
I'll make sure to submit a PR for Korean (kr) support within September.

2025년 9월 2일 (화) 오전 8:06, Sean DuBois <se...@pion.ly>님이 작성:

To view this discussion visit https://groups.google.com/d/msgid/discuss-webrtc/ECC363BB-9AD4-437C-AF88-997D4745D63B%40pion.ly.

[Harald Alvestrand]

The language dropdown seems to give you auto-translated texts, and Korean is included; I don't know how good they are.

However, we (Google) have real problems finding resources to maintain webrtc.org even in English. The most up-to-date doc source is the standards and the source code, I'm afraid (with the g3docs/ subfolder hopefully holding some helpful information for C++ at least).

To view this discussion visit https://groups.google.com/d/msgid/discuss-webrtc/CAKtnU-3F26DTRY8TVE%2B1Vf5pizscaUuZoUkuCqYuv%2B6VetTjkQ%40mail.gmail.com.

[Seonghoon Baek]

I found Korean at the very end of the language dropdown. It seems I didn't check properly due to the double scroll issue. Sorry about that, and thank you for helping me confirm it.

Of course, for studying and applying the technology, I'm also referencing the original English documents as my standard. I'm planning to refer to WebRTC's RFC documents and the W3C specifications.

If there's anything I can help with regarding webrtc.org, please feel free to reach out anytime.

Thank you so much for your response. I'll make sure to check more carefully going forward

2025년 9월 2일 (화) 오후 4:57, 'Harald Alvestrand' via discuss-webrtc <discuss...@googlegroups.com>님이 작성:

To view this discussion visit https://groups.google.com/d/msgid/discuss-webrtc/CAOqqYVHN4%3DvThz0VREzL88QEYRB3Tw4YVLJ1BKPN9G6oTXmCGg%40mail.gmail.com.