24.05.2025 Second translation

Even though, I received the first answer from the team (about me wanting to contribute to mdn russian translated content) pretty fast, I did not hear form the reviewer for over a month, even though there are rules that all of the PRs should be reviewed within 2 weeks (see image).

Nevertheless, I decided to translate another page.

This time i was translating Audio and video delivery page.

I translated the Audio and video delivery guide because it covers the end-to-end process—from encoding and buffering strategies to adaptive streaming and CDN considerations—that’s essential for building performant, user-friendly media experiences on the web. This topic is often overlooked in Russian-language resources, so by localizing these best practices and architectural insights, I’m helping fellow developers avoid common pitfalls like playback stalls or compatibility issues. Having relied on this guide myself to optimize video projects, translating it felt like the most impactful way to give back and enable non-English speakers to build smooth, resilient media applications.

This is a much bigger page (539 lines), containing not only text but also some parts of code, comments of which should also have been translated.

The translation was much easier for me since I already did one page. The link to the Pull Request. From the language side, it was a bi challenging as new technical terms were introduced, but I used a community-maintained glossary repository of web-development terms and their preferred Russian translations in order to maintain the style. All of the pages are written using Markdown which makes it even more easier to edit them.

Again, I was automatically assigned a reviewer, but after analysing their activity in that repository, I should not expect the feedback anytime soon


Comments

Leave a Reply

Your email address will not be published. Required fields are marked *