docs(ko): add Korean (ko) translation#620
Conversation
📝 WalkthroughWalkthroughThis PR adds Korean-language documentation for RustDesk client usage, build guides, self-hosting guides for OSS and Pro, plus Korean site navigation pages and Hugo language configuration. ChangesSite Index, Videos, and Configuration
Client Documentation
Developer Build Documentation
Self-hosted RustDesk Server OSS
Self-hosted RustDesk Server Pro
Estimated code review effort: 4 (Complex) | ~60 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Pull request overview
Adds a complete Korean (ko) locale to the Hugo documentation site, enabling Korean navigation/SEO metadata and providing translated content pages across the docs tree.
Changes:
- Registers the
kolanguage inhugo.yaml(title, language name, landing label, SEO description/keywords). - Adds Korean
_index.ko.mdpages across Client, Self-host (OSS/Pro), and Dev/Build sections. - Introduces Korean versions of several RustDesk Server Pro sub-guides (OIDC/Azure, LDAP, 2FA, SMTP/M365, relay, roles, etc.).
Reviewed changes
Copilot reviewed 47 out of 47 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
| hugo.yaml | Registers the ko language and its site-level params. |
| content/videos/_index.ko.md | Korean landing page for video tutorials. |
| content/self-host/rustdesk-server-pro/strategy/_index.ko.md | Korean translation for Server Pro “Strategy” docs. |
| content/self-host/rustdesk-server-pro/smtp/microsoft-365/_index.ko.md | Korean translation for SMTP OAuth2 (Microsoft 365) guide. |
| content/self-host/rustdesk-server-pro/smtp/_index.ko.md | Korean translation for SMTP overview page. |
| content/self-host/rustdesk-server-pro/relay/_index.ko.md | Korean translation for configuring extra relay servers + geo routing. |
| content/self-host/rustdesk-server-pro/permissions/_index.ko.md | Korean translation for access control/permissions guide. |
| content/self-host/rustdesk-server-pro/oidc/azure/_index.ko.md | Korean translation for Azure OIDC provider setup. |
| content/self-host/rustdesk-server-pro/oidc/_index.ko.md | Korean translation for OIDC overview page. |
| content/self-host/rustdesk-server-pro/license/_index.ko.md | Korean translation for licensing/activation/refresh/migration docs. |
| content/self-host/rustdesk-server-pro/ldap/_index.ko.md | Korean translation for LDAP configuration guide. |
| content/self-host/rustdesk-server-pro/installscript/windows/_index.ko.md | Korean translation for legacy Windows install path. |
| content/self-host/rustdesk-server-pro/installscript/Script/_index.ko.md | Korean translation for install.sh deployment path. |
| content/self-host/rustdesk-server-pro/installscript/Docker/_index.ko.md | Korean translation for Docker/Compose deployment path. |
| content/self-host/rustdesk-server-pro/installscript/_index.ko.md | Korean translation for Server Pro install landing/decision page. |
| content/self-host/rustdesk-server-pro/control-role/_index.ko.md | Korean translation for Control Role docs. |
| content/self-host/rustdesk-server-pro/console/_index.ko.md | Korean translation for the web console guide. |
| content/self-host/rustdesk-server-pro/admin-role/_index.ko.md | Korean translation for Admin Role docs. |
| content/self-host/rustdesk-server-pro/2fa/_index.ko.md | Korean translation for 2FA guide. |
| content/self-host/rustdesk-server-pro/_index.ko.md | Korean translation for Server Pro section landing page. |
| content/self-host/rustdesk-server-oss/windows/_index.ko.md | Korean translation for OSS on Windows (PM2/NSSM) guide. |
| content/self-host/rustdesk-server-oss/synology/dsm-7/_index.ko.md | Korean translation for Synology DSM 7.2 (Container Manager) guide. |
| content/self-host/rustdesk-server-oss/synology/dsm-6/_index.ko.md | Korean translation for Synology DSM 6 (legacy Docker) guide. |
| content/self-host/rustdesk-server-oss/synology/_index.ko.md | Korean translation for Synology docs index page. |
| content/self-host/rustdesk-server-oss/install/_index.ko.md | Korean translation for OSS installation overview. |
| content/self-host/rustdesk-server-oss/Docker/_index.ko.md | Korean translation for OSS Docker deployment guide. |
| content/self-host/rustdesk-server-oss/_index.ko.md | Korean translation for OSS section landing page. |
| content/self-host/nat-loopback-issues/_index.ko.md | Korean translation for NAT loopback troubleshooting. |
| content/self-host/client-deployment/_index.ko.md | Korean translation for client deployment scripting guide. |
| content/self-host/client-configuration/_index.ko.md | Korean translation for client configuration guide. |
| content/self-host/_index.ko.md | Korean translation for self-host section landing page. |
| content/dev/build/windows/_index.ko.md | Korean translation for Windows build instructions. |
| content/dev/build/osx/_index.ko.md | Korean translation for macOS build instructions. |
| content/dev/build/linux/_index.ko.md | Korean translation for Linux build instructions. |
| content/dev/build/faq/_index.ko.md | Korean translation for Windows build FAQ. |
| content/dev/build/_index.ko.md | Korean translation for build section landing page. |
| content/dev/_index.ko.md | Korean translation for dev section landing page. |
| content/client/windows/windows-portable-elevation/_index.ko.md | Korean translation for portable elevation workflow. |
| content/client/windows/MSI/_index.ko.md | Korean translation for MSI deployment docs. |
| content/client/windows/_index.ko.md | Korean translation for Windows client section landing page. |
| content/client/mac/_index.ko.md | Korean translation for macOS client guide. |
| content/client/linux/_index.ko.md | Korean translation for Linux client guide. |
| content/client/android/_index.ko.md | Korean translation for Android client guide. |
| content/client/_index.ko.md | Korean translation for client section landing page. |
| content/_index.ko.md | Korean translation for site home page. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| INFO [src/common.rs:121] **Private key comes from id_ed25519** | ||
| NFO [src/relay_server.rs:581] Key: XXXXXXXXXXXXXXXXXXXXX | ||
| INFO [src/relay_server.rs:60] #blacklist(blacklist.txt): 0 |
| ## Pro | ||
| [Youtube channel](https://youtube.com/@rustdesk) No newline at end of file |
| INFO [src/common.rs:119] relay-servers=["1xx.xxx.xxx.x7", "1xx.xxx.xxx.xx8", "7xx.xxx.xxx.xx1"] | ||
| NFO [src/rendezvous_server.rs:1467] parsed relay servers: [("1xx.xxxx.xxx.xx7", Some((-1x, xxx))), ("1xx.xxx.xxx.xx8", Some((-3x, xxx))), ("7xx.xxx.xxx.xx1", Some((6x, xxx)))] |
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Actionable comments posted: 5
Note
Due to the large number of review comments, Critical, Major severity comments were prioritized as inline comments.
🟡 Minor comments (29)
content/client/windows/MSI/_index.ko.md-87-89 (1)
87-89: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winTag the command blocks.
The fenced snippets are missing a language tag, so markdownlint keeps flagging MD040 and the commands lose syntax highlighting.
Proposed fix
- ``` + ```bat msiexec /i RustDesk-1.msi /qn INSTALLFOLDER="D:\Program Files\RustDesk" CREATESTARTMENUSHORTCUTS="Y" CREATEDESKTOPSHORTCUTS="N" INSTALLPRINTER="N" /l*v install.log - ``` + ```Apply the same fence label to the other two blocks as well.
Also applies to: 97-99, 103-105
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@content/client/windows/MSI/_index.ko.md` around lines 87 - 89, The fenced command examples in the MSI markdown are missing a language tag, which is triggering markdownlint MD040 and removing syntax highlighting. Update each fenced block in the installation examples to use the same command fence label consistently, including the blocks around the msiexec examples in the document, so all three snippets are tagged identifiably and render as command lines.Source: Linters/SAST tools
content/client/_index.ko.md-104-104 (1)
104-104: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winAdd alt text and replace the generic link label.
The screenshots at Lines 104 and 129 are still unlabeled, and Line 139 uses
hereas link text. That keeps MD045/MD059 open and hurts accessibility.Proposed fix
-  +  ... -  +  ... - [here](https://github.com/rustdesk/rustdesk/blob/bdc5cded221af9697eb29aa30babce75e987fcc9/src/core_main.rs#L242) + [RustDesk core_main.rs reference](https://github.com/rustdesk/rustdesk/blob/bdc5cded221af9697eb29aa30babce75e987fcc9/src/core_main.rs#L242)Also applies to: 129-129, 139-139
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@content/client/_index.ko.md` at line 104, The documentation images and link text in the client markdown still use unlabeled/placeholder text, so update the image references in the client content to include descriptive alt text and replace the generic “here” link label with meaningful text that describes the destination. Use the existing markdown image/link entries in the client doc to locate the unlabeled screenshots and the `here` link, and revise them to satisfy accessibility and markdown lint requirements.Source: Linters/SAST tools
content/client/mac/_index.ko.md-26-26 (1)
26-26: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winAdd alt text to the macOS screenshots.
These screenshots are unlabeled, so markdownlint will keep flagging MD045 and the page is harder to use with assistive tech.
Proposed fix
-  + Repeat the same pattern for the remaining images.
Also applies to: 30-30, 36-36, 60-60, 74-74, 78-78
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@content/client/mac/_index.ko.md` at line 26, Add descriptive alt text to each macOS screenshot image in the Korean client markdown so the markdownlint MD045 warning is resolved and the page is accessible; update the image references in the macOS docs section, including the one for the dmg screenshot and the remaining screenshots in the same file, by replacing the empty labels with meaningful descriptions that match each image’s content.Source: Linters/SAST tools
content/client/windows/windows-portable-elevation/_index.ko.md-43-43 (1)
43-43: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winAdd alt text to the portable-elevation diagrams.
These diagrams are unlabeled, so the page keeps the MD045 warnings and is harder to consume with a screen reader.
Proposed fix
-  + Apply the same pattern to the remaining diagram images.
Also applies to: 51-51, 53-53
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@content/client/windows/windows-portable-elevation/_index.ko.md` at line 43, The portable-elevation diagram images in the markdown still lack alt text, which is triggering MD045 and hurts screen-reader accessibility. Update the image markup in this document by adding descriptive alt text to the diagram references used in the portable-elevation section, following the same pattern for the remaining images referenced alongside this one. Use the image entries themselves as the target locations so the fix stays consistent across the section.Source: Linters/SAST tools
content/client/android/_index.ko.md-17-17 (1)
17-17: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winAdd alt text to every screenshot.
Every image in this page is still anonymous, so MD045 keeps firing and screen readers have nothing useful to announce.
Proposed fix
-  + Apply the same pattern to the remaining screenshot/table images.
Also applies to: 23-23, 39-39, 55-55, 73-73, 89-89, 107-107, 113-113, 136-136, 146-146, 152-152
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@content/client/android/_index.ko.md` at line 17, Add descriptive alt text to every screenshot image in the Android markdown page to satisfy MD045 and make the images accessible. Update the anonymous image syntax in the table entries and any other screenshot references by using meaningful alt text that describes each screen, applying the same pattern consistently across the remaining image locations in this document. Use the existing image references in the markdown as the anchors to locate all affected screenshots and ensure none remain blank.Source: Linters/SAST tools
content/client/_index.ko.md-35-35 (1)
35-35: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick winKeep the Korean landing page inside the ko tree.
Both links hard-code
/docs/en/..., so Korean readers get bounced back to English pages even though the ko pages exist in this PR.Proposed fix
- [macOS page](https://rustdesk.com/docs/en/client/mac/) + [macOS 페이지](/docs/ko/client/mac/) ... - 자세한 정보는 [Android page](https://rustdesk.com/docs/en/client/android/)에서 확인할 수 있습니다. + 자세한 정보는 [Android 페이지](/docs/ko/client/android/)에서 확인할 수 있습니다.Also applies to: 96-96
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@content/client/_index.ko.md` at line 35, The Korean landing page text still points readers to English documentation, which should stay within the ko tree. Update the hard-coded /docs/en/ targets in the Korean landing page content for the GitHub download link and the macOS page link so they point to the corresponding Korean pages instead. Make the same localization change anywhere else in this PR with the same link pattern so Korean readers stay on the Korean docs path.content/client/windows/_index.ko.md-14-16 (1)
14-16: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick winDon't self-link the "standard installation" row.
/docs/ko/client/windows/resolves to this page, so the first row doesn't take readers anywhere useful. Point it at the general Korean client overview instead.Proposed fix
- | 표준 Windows 클라이언트 설치 | [Windows client overview](/docs/ko/client/windows/) | + | 표준 Windows 클라이언트 설치 | [Windows 클라이언트 개요](/docs/ko/client/) |🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@content/client/windows/_index.ko.md` around lines 14 - 16, The “standard Windows client installation” row is self-linking to the same page and should instead point to the general Korean client overview. Update the first link in the Windows table in the `_index.ko.md` content so it uses the broader client overview target, while leaving the MSI and Windows Portable Elevation rows unchanged.content/client/_index.ko.md-88-93 (1)
88-93: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winLabel the Nix snippet.
The fenced config block is unlabeled, so markdownlint keeps flagging it and the snippet loses syntax highlighting.
Proposed fix
- ``` + ```nix environment.systemPackages = with pkgs; [ ... rustdesk ]; - ``` + ```🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@content/client/_index.ko.md` around lines 88 - 93, The fenced Nix config snippet in the markdown content is missing a language label, which causes markdownlint warnings and no syntax highlighting. Update the fenced block in the relevant markdown section to use the Nix language identifier, keeping the snippet content unchanged; locate the fence around the environment.systemPackages example and add the label to that block.Source: Linters/SAST tools
content/videos/_index.ko.md-22-22 (1)
22-22: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winCapitalize “YouTube” in the link label.
Small wording fix, but the current label breaks the platform’s official name.
Proposed fix
-[Youtube channel](https://youtube.com/@rustdesk) +[YouTube channel](https://youtube.com/@rustdesk)🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@content/videos/_index.ko.md` at line 22, The link label in the Korean videos index uses the incorrect platform name capitalization. Update the markdown label for the existing YouTube link so it matches the official “YouTube” spelling, keeping the same target URL and surrounding content unchanged.Source: Linters/SAST tools
content/_index.ko.md-10-10 (1)
10-10: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winSeparate the OSS and Pro product names here.
This sentence repeats
전문 서버for both paths, which makes the intro misleading and conflicts with the OSS/Pro links below.Proposed fix
- ...저희 [website](https://rustdesk.com)에서 구매 가능한 완벽한 기능의 **전문 서버**와 기본 무료 및 오픈소스 소프트웨어인 저희 **전문 서버**를 기반으로 한 서버 중에서 선택할 수 있습니다. + ...저희 [website](https://rustdesk.com)에서 구매 가능한 완벽한 기능의 **전문 서버(Pro)** 와 무료 오픈소스 **RustDesk Server OSS** 중에서 선택할 수 있습니다.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@content/_index.ko.md` at line 10, The Korean intro sentence uses the same product name for both the paid and OSS paths, so update the wording in the opening paragraph to clearly distinguish the Pro server from the OSS/self-hosted server. Keep the existing links, but replace the repeated “전문 서버” label so the first reference matches the commercial product and the second matches the open-source/server offering used elsewhere in the page.content/self-host/rustdesk-server-pro/console/_index.ko.md-65-65 (1)
65-65: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick winPoint these links at the ko pages.
Both destinations still point at the English docs even though the translated client-config/deployment pages already exist in this PR. Keeping the links local avoids bouncing readers out of the Korean site.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@content/self-host/rustdesk-server-pro/console/_index.ko.md` at line 65, Update the links in the Korean console page so they point to the localized ko documentation instead of the English docs. In the sentence containing the client config and deployment scripts references, replace the current URLs with the matching Korean pages already present in this PR, keeping the references local within the Korean site.content/self-host/rustdesk-server-pro/faq/_index.ko.md-181-181 (1)
181-181: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick winFix the sales email link.
mailto://isn't a valid email URI here, so browsers will treat it as a broken link. Usemailto:sales@rustdesk.com.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@content/self-host/rustdesk-server-pro/faq/_index.ko.md` at line 181, The sales contact link is using an invalid mailto URI in the FAQ content, so update the existing sales link markup to use the correct mailto scheme in the same markdown section. Adjust the hyperlink target associated with the sales team reference so it points to sales@rustdesk.com with a valid mailto: URI and preserves the surrounding Korean text.content/self-host/rustdesk-server-pro/_index.ko.md-41-45 (1)
41-45: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick winKeep the locale links in Korean.
This section still sends readers to English docs in a few places, and the
#log-intarget should be rechecked against the Korean heading. Please swap these to the ko URLs/anchors so the translated page stays self-contained.Also applies to: 63-100
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@content/self-host/rustdesk-server-pro/_index.ko.md` around lines 41 - 45, The Korean self-host page still links to English docs and an English-only anchor, so update the localized references in the notice blocks and the login section to point to the ko versions. Fix the markdown links in this document so they use the Korean URLs and verify the `#log-in` target matches the Korean heading used later in the page. Keep the translated page self-contained by checking the related link blocks throughout the self-host section, especially the notice text and the login-related anchor link.content/self-host/rustdesk-server-pro/2fa/_index.ko.md-25-25 (1)
25-25: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick winUse “비밀 데이터” instead of “비밀번호” here.
Expired 2FA reactivation updates the secret/backup material, not a password; keep the quick answer and note wording consistent.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@content/self-host/rustdesk-server-pro/2fa/_index.ko.md` at line 25, The wording in the 2FA Korean copy is incorrect: the reactivation flow updates secret data, not a password. Update the sentence in the 2FA markdown content to replace “비밀번호” with “비밀 데이터” while keeping the rest of the quick explanation consistent and concise.content/self-host/rustdesk-server-pro/installscript/Script/_index.ko.md-48-49 (1)
48-49: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick winChange both
443(HTTP)mentions to HTTPS.Port 443 is the HTTPS endpoint here, so labeling it HTTP is misleading in two places and can send operators down the wrong setup path.
Fix
- ... 포트 `443`(HTTP) ... + ... 포트 `443`(HTTPS) ...Also applies to: 101-102
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@content/self-host/rustdesk-server-pro/installscript/Script/_index.ko.md` around lines 48 - 49, The wording in the domain/SSL setup text incorrectly labels port 443 as HTTP in the installscript markdown, which is misleading in both occurrences. Update the affected sentence in _index.ko.md to describe port 443 as HTTPS while keeping the rest of the Nginx/Certbot and certificate renewal guidance unchanged, and make the same wording correction wherever the duplicated text appears in the related section.content/self-host/rustdesk-server-pro/smtp/microsoft-365/_index.ko.md-174-187 (1)
174-187: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winRemove the pasted placeholder lines.
The block between the mailbox example and the next paragraph looks like an accidental paste artifact and breaks the flow. Deleting it will restore the step sequence.
Cleanup
-이미 존재합니다 -서비스 -서버 -별명 - -🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@content/self-host/rustdesk-server-pro/smtp/microsoft-365/_index.ko.md` around lines 174 - 187, Remove the accidental pasted placeholder block in the Microsoft 365 SMTP guide so the mailbox example flows directly into the next paragraph. Edit the _index.ko.md content around the shared mailbox example and delete the stray standalone lines (“이미 존재합니다”, “서비스”, “서버”, “별명”) that are not part of the instructions. Keep the existing guidance about verifying the value used with Add-MailboxPermission and preserve the surrounding mailbox example and explanation.content/self-host/rustdesk-server-pro/installscript/Script/_index.ko.md-52-53 (1)
52-53: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick winPin the translated heading’s anchor
## 오픈소스에서 변환하기no longer generates#convert-from-open-source, and there’s no explicit ID override here, so any links to that anchor will break. Add{#convert-from-open-source}to keep the existing jump stable.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@content/self-host/rustdesk-server-pro/installscript/Script/_index.ko.md` around lines 52 - 53, The translated heading in the Markdown page is losing the existing anchor, so links to the old jump target will break. Update the heading that renders “오픈소스에서 변환하기” to include the explicit ID override `{`#convert-from-open-source`}` in the same place so the anchor stays stable; use the heading markup in this `_index.ko.md` section as the target.content/self-host/client-configuration/_index.ko.md-40-41 (1)
40-41: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winAdd alt text to the screenshots.
These image-only figures trip MD045 and leave screen readers without context. A short description on each image is enough.
♻️ Example fix
-  + Also applies to: 47-47, 69-69, 97-97
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@content/self-host/client-configuration/_index.ko.md` around lines 40 - 41, The screenshot images in this markdown page are missing alt text, which triggers MD045 and leaves screen readers without context. Update each image reference in the client configuration document to include a short, meaningful description that identifies the screenshot content, and apply the same fix to the other image occurrences noted in the review. Use the existing image references in _index.ko.md as the targets and keep the descriptions brief but specific.Source: Linters/SAST tools
content/self-host/nat-loopback-issues/_index.ko.md-73-73 (1)
73-73: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winAdd alt text to the screenshots.
These image-only figures trip MD045 and leave screen readers without context.
♻️ Example fix
-  + Also applies to: 78-78, 83-83, 87-87, 95-95, 102-102
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@content/self-host/nat-loopback-issues/_index.ko.md` at line 73, Add descriptive alt text to each screenshot image in the markdown so the figure content is accessible and no longer triggers MD045. Update the image-only entries in the nat-loopback-issues page to include meaningful descriptions that match each screenshot’s purpose, using the existing image references as the anchor points. Repeat this for all affected image tags in the document so screen readers have context throughout.Source: Linters/SAST tools
content/self-host/rustdesk-server-oss/_index.ko.md-27-27 (1)
27-27: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winLocalize the NAT loopback link.
This notice still sends readers to the English article even though the Korean translation ships in this PR. Point it at the ko page so the self-hosting flow stays in one locale.
♻️ Proposed fix
- [this article](https://rustdesk.com/docs/en/self-host/nat-loopback-issues/) + [이 문서](/docs/ko/self-host/nat-loopback-issues/)🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@content/self-host/rustdesk-server-oss/_index.ko.md` at line 27, The self-hosting notice in the Korean docs still links to the English NAT loopback article, so update the markdown in the localized `_index.ko.md` content to point to the Korean version of the same article instead. Keep the link text and surrounding guidance the same, and adjust only the destination URL so readers stay within the ko locale.content/self-host/nat-loopback-issues/_index.ko.md-36-38 (1)
36-38: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick winUse a documentation-safe example IP.
172.16.16.1is RFC1918 private space, so calling it the router's public IP makes the example self-contradictory. Swap in a reserved public example such as203.0.113.1, or label it as an example address instead.♻️ Proposed fix
- 라우터의 공인 IP는 `172.16.16.1`이고 + 라우터의 공인 IP 예시는 `203.0.113.1`이고🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@content/self-host/nat-loopback-issues/_index.ko.md` around lines 36 - 38, The example in the nat-loopback-issues documentation uses `172.16.16.1` as the router’s public IP, which conflicts with RFC1918 private space. Update the example in the affected paragraph to use a documentation-safe public example address such as `203.0.113.1`, or clearly label it as a non-public example, and keep the rest of the NAT/port-forwarding explanation consistent with the new address.content/self-host/rustdesk-server-oss/install/_index.ko.md-67-67 (1)
67-67: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick winFix the
.debinstall command.
apt-get -f installdoes not install a local.debfile here, so this example will fail as written. Usedpkg -ifollowed bysudo apt-get -f installfor dependency repair, or switch tosudo apt install ./<filename>.deb.♻️ Proposed fix
- [Download](https://github.com/rustdesk/rustdesk-server/releases/latest) deb 파일을 직접 다운로드하여 `apt-get -f install <filename>.deb` 또는 `dpkg -i <filename>.deb`로 설치해 주세요. + [Download](https://github.com/rustdesk/rustdesk-server/releases/latest) deb 파일을 직접 다운로드하여 `dpkg -i <filename>.deb`로 설치한 다음, 필요한 경우 `sudo apt-get -f install`로 의존성을 정리해 주세요.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@content/self-host/rustdesk-server-oss/install/_index.ko.md` at line 67, The install example in the Rustdesk server OSS Korean docs uses an invalid local .deb flow by pairing apt-get -f install with a filename, so update the instruction to use dpkg -i for the downloaded package and then apt-get -f install for dependency repair, or replace the whole example with apt install ./<filename>.deb. Keep the change in the install markdown content and ensure the command sequence around the .deb download is consistent with the package manager behavior.content/self-host/rustdesk-server-oss/Docker/_index.ko.md-97-97 (1)
97-97: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick winKeep the compose filename consistent.
The sample uses
compose.yml, but this sentence switches todocker-compose.yml, so readers will edit the wrong file. Update the text to match the example.♻️ Proposed fix
- config 변경이 필요한 경우, 예를 들어 ALWAYS_USE_RELAY=Y를 설정하려면 docker-compose.yml의 환경을 사용할 수 있습니다. + config 변경이 필요한 경우, 예를 들어 ALWAYS_USE_RELAY=Y를 설정하려면 compose.yml의 `environment` 섹션을 사용할 수 있습니다.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@content/self-host/rustdesk-server-oss/Docker/_index.ko.md` at line 97, Keep the compose filename consistent in the Korean Docker docs sentence: it currently refers to docker-compose.yml while the surrounding example uses compose.yml. Update the wording in the markdown content so it matches the same compose file name used elsewhere in this section, preserving consistency for readers.content/self-host/client-configuration/_index.ko.md-93-93 (1)
93-93: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winKeep the deployment link on the Korean site.
This jumps to the English deployment page even though the localized page exists in this PR. Switching to the ko route keeps readers in the same locale.
♻️ Proposed fix
- 자동으로 설정하는 가장 쉬운 방법은 [here](https://rustdesk.com/docs/en/self-host/client-deployment/)에서 찾을 수 있습니다. + 자동으로 설정하는 가장 쉬운 방법은 [클라이언트 배포 가이드](/docs/ko/self-host/client-deployment/)에서 찾을 수 있습니다.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@content/self-host/client-configuration/_index.ko.md` at line 93, The deployment link in the Korean client configuration doc should point to the localized ko route instead of the English page. Update the existing markdown link in the Korean content file so it uses the Korean deployment documentation path, keeping readers on the same locale while preserving the same deployment-script reference.content/self-host/rustdesk-server-oss/synology/dsm-7/_index.ko.md-35-92 (1)
35-92: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winAdd alt text to the screenshots.
The empty
placeholders make this walkthrough inaccessible to screen-reader users and keep tripping the markdown linter. Short descriptive labels on each image would be enough.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@content/self-host/rustdesk-server-oss/synology/dsm-7/_index.ko.md` around lines 35 - 92, The screenshots in this guide are missing alt text, which breaks accessibility and markdown linting. Update each image reference in the Synology DSM 7 document to include a short descriptive label that explains what the screenshot shows, using the existing image spots in the section so the walkthrough remains readable for screen-reader users.Source: Linters/SAST tools
content/self-host/client-configuration/advanced-settings/_index.ko.md-204-204 (1)
204-204: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winFix the intra-page anchor.
#privacy-modedoesn't match the translated heading below, so this link will break in the Korean build. Please point it at the actual rendered slug or give the heading an explicit id.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@content/self-host/client-configuration/advanced-settings/_index.ko.md` at line 204, The intra-page link in the Korean advanced-settings markdown points to a translated heading that does not exist in the rendered slug, so the anchor will break. Update the `privacy-mode` reference in this section to target the actual generated anchor for the Korean heading, or assign that heading an explicit id and reference it consistently so the link resolves correctly.Source: Linters/SAST tools
content/self-host/client-configuration/advanced-settings/_index.ko.md-336-338 (1)
336-338: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winComplete the missing table column.
This row only has three cells under a four-column header, so the Markdown table renders misaligned. Add the missing
Defaultvalue or split the option into separate rows.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@content/self-host/client-configuration/advanced-settings/_index.ko.md` around lines 336 - 338, The Markdown table in the advanced settings doc has one fewer cell than the “Install required / Values / Default / Example” header, causing misalignment. Update the row in the table so it matches the four-column structure by adding the missing Default value or by splitting the option into separate rows, and keep the change within the relevant table block in _index.ko.md.Source: Linters/SAST tools
content/self-host/client-deployment/_index.ko.md-33-35 (1)
33-35: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winKeep the cross-links in the ko locale.
Both URLs still point to the English docs, even though the Korean translations exist in this PR. Switching them to the
/docs/ko/...pages keeps readers in the localized flow.Possible fix
- [Client Configuration](https://rustdesk.com/docs/en/self-host/client-configuration/) + [Client Configuration](/docs/ko/self-host/client-configuration/)Apply the same locale swap to the MSI link below.
Also applies to: 209-211
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@content/self-host/client-deployment/_index.ko.md` around lines 33 - 35, The localized client deployment docs still link to English pages, so update the cross-links in the Korean markdown to point to the Korean equivalents instead. In the content around the Client Configuration reference and the MSI link below, switch the URLs from the /docs/en/ paths to the matching /docs/ko/ paths so the _index.ko.md page stays fully localized.content/self-host/rustdesk-server-oss/synology/dsm-6/_index.ko.md-34-83 (1)
34-83: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winAdd alt text to the screenshots.
The empty
placeholders make this walkthrough inaccessible to screen-reader users and keep tripping the markdown linter. Short descriptive labels on each image would be enough.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@content/self-host/rustdesk-server-oss/synology/dsm-6/_index.ko.md` around lines 34 - 83, The screenshots in this walkthrough are missing alt text, which hurts accessibility and triggers the markdown linter. Update each empty image label in this document with a short descriptive alt string that matches the image content, using the existing image references as-is. Focus on the screenshot entries around the RustDesk setup steps so the alt text clearly identifies each UI state.Source: Linters/SAST tools
🧹 Nitpick comments (3)
content/self-host/rustdesk-server-pro/installscript/Docker/_index.ko.md (1)
60-62: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick winKeep the FAQ links localized.
These notices still point to the English FAQ. If the Korean FAQ page covers the same steps, switch both links to the localized page so readers stay in the
kodocs flow.Also applies to: 82-94
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@content/self-host/rustdesk-server-pro/installscript/Docker/_index.ko.md` around lines 60 - 62, The FAQ notice links in the Korean Docker install guide still point to the English documentation, so update the markdown in the localized `_index.ko.md` notices to use the Korean FAQ URL instead. Make the same link change in both affected notice blocks so the `ko` docs stay consistent, and keep the existing notice text and structure unchanged.content/self-host/rustdesk-server-pro/smtp/microsoft-365/_index.ko.md (1)
25-223: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick winAdd alt text to the screenshots.
All screenshot references on this page use empty alt text, which triggers MD045 and hurts accessibility. Please add concise descriptions to each image.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@content/self-host/rustdesk-server-pro/smtp/microsoft-365/_index.ko.md` around lines 25 - 223, The page’s screenshot images currently use empty alt text, which triggers MD045 and reduces accessibility. Update each image reference in the Microsoft 365 SMTP guide to include a brief, descriptive alt text that matches the screenshot content. Keep the descriptions concise and consistent across all image entries in this document.Source: Linters/SAST tools
content/self-host/rustdesk-server-pro/strategy/_index.ko.md (1)
40-78: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick winAdd alt text to the strategy screenshots.
The page's screenshots use empty alt text, so MD045 will keep firing and screen-reader users get no context. Short descriptions for each image would fix both.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@content/self-host/rustdesk-server-pro/strategy/_index.ko.md` around lines 40 - 78, Update the strategy screenshot image references in the strategy guide to use descriptive alt text instead of empty alt text. Replace the blank image descriptions for the screenshots in this section with short, meaningful labels that describe each screenshot, using the existing image markup near the strategy overview, Edit Devices, Edit Users, and Edit Device Group content so the Markdown lint MD045 warning is resolved and the images are accessible.Source: Linters/SAST tools
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@content/client/linux/_index.ko.md`:
- Around line 71-75: The Ubuntu AppImage prerequisite command is using the wrong
package manager, so update the Linux client docs snippet to use Ubuntu’s
apt-based install path instead of yum. In the AppImage setup section of the
Ubuntu instructions, replace the Fedora/RHEL reference with the correct Ubuntu
package name and note the 24.04+ variant if needed. Keep the surrounding
AppImage launch step unchanged.
In `@content/self-host/client-deployment/_index.ko.md`:
- Around line 35-37: The deployment-script examples in the client deployment
docs currently tell users to print the generated unattended-access password to
stdout, which should be avoided for managed rollout tooling. Update the relevant
examples in the document to keep the password local/secret-only instead of
emitting it, and adjust the surrounding text near the affected deployment
sections so it no longer instructs users to capture the password from script
output.
In `@content/self-host/rustdesk-server-pro/faq/_index.ko.md`:
- Around line 215-237: The PowerShell updater snippet is hard-coding RustDesk
version 1.2.6, which makes the FAQ install an outdated build. Update the update
flow in this section to avoid embedding a fixed release number in the $rdver
check and Invoke-WebRequest URL, and instead use a dynamic/current release
source or replace the example with a maintained updater approach so the script
always fetches the latest supported version.
- Around line 504-511: The SELinux guidance in the FAQ uses bare binary names in
the semanage fcontext commands, which won’t match the installed executables.
Update the SELinux rule examples in the RustDesk Relay section to use the full
install paths for both hbbs and hbbr, and keep the restorecon examples aligned
with those same installed binary paths.
- Around line 129-136: The systemd examples in the FAQ use a pipeline character
that makes the commands incorrect. Update the examples in the relevant FAQ
entries so each `systemctl` action is shown as separate invocations for
`rustdesk-hbbs` and `rustdesk-hbbr` instead of `rustdesk-hbbs|rustdesk-hbbr`,
and keep the surrounding text in the same section consistent with the corrected
command usage.
---
Minor comments:
In `@content/_index.ko.md`:
- Line 10: The Korean intro sentence uses the same product name for both the
paid and OSS paths, so update the wording in the opening paragraph to clearly
distinguish the Pro server from the OSS/self-hosted server. Keep the existing
links, but replace the repeated “전문 서버” label so the first reference matches the
commercial product and the second matches the open-source/server offering used
elsewhere in the page.
In `@content/client/_index.ko.md`:
- Line 104: The documentation images and link text in the client markdown still
use unlabeled/placeholder text, so update the image references in the client
content to include descriptive alt text and replace the generic “here” link
label with meaningful text that describes the destination. Use the existing
markdown image/link entries in the client doc to locate the unlabeled
screenshots and the `here` link, and revise them to satisfy accessibility and
markdown lint requirements.
- Line 35: The Korean landing page text still points readers to English
documentation, which should stay within the ko tree. Update the hard-coded
/docs/en/ targets in the Korean landing page content for the GitHub download
link and the macOS page link so they point to the corresponding Korean pages
instead. Make the same localization change anywhere else in this PR with the
same link pattern so Korean readers stay on the Korean docs path.
- Around line 88-93: The fenced Nix config snippet in the markdown content is
missing a language label, which causes markdownlint warnings and no syntax
highlighting. Update the fenced block in the relevant markdown section to use
the Nix language identifier, keeping the snippet content unchanged; locate the
fence around the environment.systemPackages example and add the label to that
block.
In `@content/client/android/_index.ko.md`:
- Line 17: Add descriptive alt text to every screenshot image in the Android
markdown page to satisfy MD045 and make the images accessible. Update the
anonymous image syntax in the table entries and any other screenshot references
by using meaningful alt text that describes each screen, applying the same
pattern consistently across the remaining image locations in this document. Use
the existing image references in the markdown as the anchors to locate all
affected screenshots and ensure none remain blank.
In `@content/client/mac/_index.ko.md`:
- Line 26: Add descriptive alt text to each macOS screenshot image in the Korean
client markdown so the markdownlint MD045 warning is resolved and the page is
accessible; update the image references in the macOS docs section, including the
one for the dmg screenshot and the remaining screenshots in the same file, by
replacing the empty labels with meaningful descriptions that match each image’s
content.
In `@content/client/windows/_index.ko.md`:
- Around line 14-16: The “standard Windows client installation” row is
self-linking to the same page and should instead point to the general Korean
client overview. Update the first link in the Windows table in the
`_index.ko.md` content so it uses the broader client overview target, while
leaving the MSI and Windows Portable Elevation rows unchanged.
In `@content/client/windows/MSI/_index.ko.md`:
- Around line 87-89: The fenced command examples in the MSI markdown are missing
a language tag, which is triggering markdownlint MD040 and removing syntax
highlighting. Update each fenced block in the installation examples to use the
same command fence label consistently, including the blocks around the msiexec
examples in the document, so all three snippets are tagged identifiably and
render as command lines.
In `@content/client/windows/windows-portable-elevation/_index.ko.md`:
- Line 43: The portable-elevation diagram images in the markdown still lack alt
text, which is triggering MD045 and hurts screen-reader accessibility. Update
the image markup in this document by adding descriptive alt text to the diagram
references used in the portable-elevation section, following the same pattern
for the remaining images referenced alongside this one. Use the image entries
themselves as the target locations so the fix stays consistent across the
section.
In `@content/self-host/client-configuration/_index.ko.md`:
- Around line 40-41: The screenshot images in this markdown page are missing alt
text, which triggers MD045 and leaves screen readers without context. Update
each image reference in the client configuration document to include a short,
meaningful description that identifies the screenshot content, and apply the
same fix to the other image occurrences noted in the review. Use the existing
image references in _index.ko.md as the targets and keep the descriptions brief
but specific.
- Line 93: The deployment link in the Korean client configuration doc should
point to the localized ko route instead of the English page. Update the existing
markdown link in the Korean content file so it uses the Korean deployment
documentation path, keeping readers on the same locale while preserving the same
deployment-script reference.
In `@content/self-host/client-configuration/advanced-settings/_index.ko.md`:
- Line 204: The intra-page link in the Korean advanced-settings markdown points
to a translated heading that does not exist in the rendered slug, so the anchor
will break. Update the `privacy-mode` reference in this section to target the
actual generated anchor for the Korean heading, or assign that heading an
explicit id and reference it consistently so the link resolves correctly.
- Around line 336-338: The Markdown table in the advanced settings doc has one
fewer cell than the “Install required / Values / Default / Example” header,
causing misalignment. Update the row in the table so it matches the four-column
structure by adding the missing Default value or by splitting the option into
separate rows, and keep the change within the relevant table block in
_index.ko.md.
In `@content/self-host/client-deployment/_index.ko.md`:
- Around line 33-35: The localized client deployment docs still link to English
pages, so update the cross-links in the Korean markdown to point to the Korean
equivalents instead. In the content around the Client Configuration reference
and the MSI link below, switch the URLs from the /docs/en/ paths to the matching
/docs/ko/ paths so the _index.ko.md page stays fully localized.
In `@content/self-host/nat-loopback-issues/_index.ko.md`:
- Line 73: Add descriptive alt text to each screenshot image in the markdown so
the figure content is accessible and no longer triggers MD045. Update the
image-only entries in the nat-loopback-issues page to include meaningful
descriptions that match each screenshot’s purpose, using the existing image
references as the anchor points. Repeat this for all affected image tags in the
document so screen readers have context throughout.
- Around line 36-38: The example in the nat-loopback-issues documentation uses
`172.16.16.1` as the router’s public IP, which conflicts with RFC1918 private
space. Update the example in the affected paragraph to use a documentation-safe
public example address such as `203.0.113.1`, or clearly label it as a
non-public example, and keep the rest of the NAT/port-forwarding explanation
consistent with the new address.
In `@content/self-host/rustdesk-server-oss/_index.ko.md`:
- Line 27: The self-hosting notice in the Korean docs still links to the English
NAT loopback article, so update the markdown in the localized `_index.ko.md`
content to point to the Korean version of the same article instead. Keep the
link text and surrounding guidance the same, and adjust only the destination URL
so readers stay within the ko locale.
In `@content/self-host/rustdesk-server-oss/Docker/_index.ko.md`:
- Line 97: Keep the compose filename consistent in the Korean Docker docs
sentence: it currently refers to docker-compose.yml while the surrounding
example uses compose.yml. Update the wording in the markdown content so it
matches the same compose file name used elsewhere in this section, preserving
consistency for readers.
In `@content/self-host/rustdesk-server-oss/install/_index.ko.md`:
- Line 67: The install example in the Rustdesk server OSS Korean docs uses an
invalid local .deb flow by pairing apt-get -f install with a filename, so update
the instruction to use dpkg -i for the downloaded package and then apt-get -f
install for dependency repair, or replace the whole example with apt install
./<filename>.deb. Keep the change in the install markdown content and ensure the
command sequence around the .deb download is consistent with the package manager
behavior.
In `@content/self-host/rustdesk-server-oss/synology/dsm-6/_index.ko.md`:
- Around line 34-83: The screenshots in this walkthrough are missing alt text,
which hurts accessibility and triggers the markdown linter. Update each empty
image label in this document with a short descriptive alt string that matches
the image content, using the existing image references as-is. Focus on the
screenshot entries around the RustDesk setup steps so the alt text clearly
identifies each UI state.
In `@content/self-host/rustdesk-server-oss/synology/dsm-7/_index.ko.md`:
- Around line 35-92: The screenshots in this guide are missing alt text, which
breaks accessibility and markdown linting. Update each image reference in the
Synology DSM 7 document to include a short descriptive label that explains what
the screenshot shows, using the existing image spots in the section so the
walkthrough remains readable for screen-reader users.
In `@content/self-host/rustdesk-server-pro/_index.ko.md`:
- Around line 41-45: The Korean self-host page still links to English docs and
an English-only anchor, so update the localized references in the notice blocks
and the login section to point to the ko versions. Fix the markdown links in
this document so they use the Korean URLs and verify the `#log-in` target
matches the Korean heading used later in the page. Keep the translated page
self-contained by checking the related link blocks throughout the self-host
section, especially the notice text and the login-related anchor link.
In `@content/self-host/rustdesk-server-pro/2fa/_index.ko.md`:
- Line 25: The wording in the 2FA Korean copy is incorrect: the reactivation
flow updates secret data, not a password. Update the sentence in the 2FA
markdown content to replace “비밀번호” with “비밀 데이터” while keeping the rest of the
quick explanation consistent and concise.
In `@content/self-host/rustdesk-server-pro/console/_index.ko.md`:
- Line 65: Update the links in the Korean console page so they point to the
localized ko documentation instead of the English docs. In the sentence
containing the client config and deployment scripts references, replace the
current URLs with the matching Korean pages already present in this PR, keeping
the references local within the Korean site.
In `@content/self-host/rustdesk-server-pro/faq/_index.ko.md`:
- Line 181: The sales contact link is using an invalid mailto URI in the FAQ
content, so update the existing sales link markup to use the correct mailto
scheme in the same markdown section. Adjust the hyperlink target associated with
the sales team reference so it points to sales@rustdesk.com with a valid mailto:
URI and preserves the surrounding Korean text.
In `@content/self-host/rustdesk-server-pro/installscript/Script/_index.ko.md`:
- Around line 48-49: The wording in the domain/SSL setup text incorrectly labels
port 443 as HTTP in the installscript markdown, which is misleading in both
occurrences. Update the affected sentence in _index.ko.md to describe port 443
as HTTPS while keeping the rest of the Nginx/Certbot and certificate renewal
guidance unchanged, and make the same wording correction wherever the duplicated
text appears in the related section.
- Around line 52-53: The translated heading in the Markdown page is losing the
existing anchor, so links to the old jump target will break. Update the heading
that renders “오픈소스에서 변환하기” to include the explicit ID override
`{`#convert-from-open-source`}` in the same place so the anchor stays stable; use
the heading markup in this `_index.ko.md` section as the target.
In `@content/self-host/rustdesk-server-pro/smtp/microsoft-365/_index.ko.md`:
- Around line 174-187: Remove the accidental pasted placeholder block in the
Microsoft 365 SMTP guide so the mailbox example flows directly into the next
paragraph. Edit the _index.ko.md content around the shared mailbox example and
delete the stray standalone lines (“이미 존재합니다”, “서비스”, “서버”, “별명”) that are not
part of the instructions. Keep the existing guidance about verifying the value
used with Add-MailboxPermission and preserve the surrounding mailbox example and
explanation.
In `@content/videos/_index.ko.md`:
- Line 22: The link label in the Korean videos index uses the incorrect platform
name capitalization. Update the markdown label for the existing YouTube link so
it matches the official “YouTube” spelling, keeping the same target URL and
surrounding content unchanged.
---
Nitpick comments:
In `@content/self-host/rustdesk-server-pro/installscript/Docker/_index.ko.md`:
- Around line 60-62: The FAQ notice links in the Korean Docker install guide
still point to the English documentation, so update the markdown in the
localized `_index.ko.md` notices to use the Korean FAQ URL instead. Make the
same link change in both affected notice blocks so the `ko` docs stay
consistent, and keep the existing notice text and structure unchanged.
In `@content/self-host/rustdesk-server-pro/smtp/microsoft-365/_index.ko.md`:
- Around line 25-223: The page’s screenshot images currently use empty alt text,
which triggers MD045 and reduces accessibility. Update each image reference in
the Microsoft 365 SMTP guide to include a brief, descriptive alt text that
matches the screenshot content. Keep the descriptions concise and consistent
across all image entries in this document.
In `@content/self-host/rustdesk-server-pro/strategy/_index.ko.md`:
- Around line 40-78: Update the strategy screenshot image references in the
strategy guide to use descriptive alt text instead of empty alt text. Replace
the blank image descriptions for the screenshots in this section with short,
meaningful labels that describe each screenshot, using the existing image markup
near the strategy overview, Edit Devices, Edit Users, and Edit Device Group
content so the Markdown lint MD045 warning is resolved and the images are
accessible.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 022ec407-5e99-4e2c-809d-fe6f491c28fc
📒 Files selected for processing (47)
content/_index.ko.mdcontent/client/_index.ko.mdcontent/client/android/_index.ko.mdcontent/client/linux/_index.ko.mdcontent/client/mac/_index.ko.mdcontent/client/windows/MSI/_index.ko.mdcontent/client/windows/_index.ko.mdcontent/client/windows/windows-portable-elevation/_index.ko.mdcontent/dev/_index.ko.mdcontent/dev/build/_index.ko.mdcontent/dev/build/faq/_index.ko.mdcontent/dev/build/linux/_index.ko.mdcontent/dev/build/osx/_index.ko.mdcontent/dev/build/windows/_index.ko.mdcontent/self-host/_index.ko.mdcontent/self-host/client-configuration/_index.ko.mdcontent/self-host/client-configuration/advanced-settings/_index.ko.mdcontent/self-host/client-deployment/_index.ko.mdcontent/self-host/nat-loopback-issues/_index.ko.mdcontent/self-host/rustdesk-server-oss/Docker/_index.ko.mdcontent/self-host/rustdesk-server-oss/_index.ko.mdcontent/self-host/rustdesk-server-oss/install/_index.ko.mdcontent/self-host/rustdesk-server-oss/synology/_index.ko.mdcontent/self-host/rustdesk-server-oss/synology/dsm-6/_index.ko.mdcontent/self-host/rustdesk-server-oss/synology/dsm-7/_index.ko.mdcontent/self-host/rustdesk-server-oss/windows/_index.ko.mdcontent/self-host/rustdesk-server-pro/2fa/_index.ko.mdcontent/self-host/rustdesk-server-pro/_index.ko.mdcontent/self-host/rustdesk-server-pro/admin-role/_index.ko.mdcontent/self-host/rustdesk-server-pro/console/_index.ko.mdcontent/self-host/rustdesk-server-pro/control-role/_index.ko.mdcontent/self-host/rustdesk-server-pro/faq/_index.ko.mdcontent/self-host/rustdesk-server-pro/installscript/Docker/_index.ko.mdcontent/self-host/rustdesk-server-pro/installscript/Script/_index.ko.mdcontent/self-host/rustdesk-server-pro/installscript/_index.ko.mdcontent/self-host/rustdesk-server-pro/installscript/windows/_index.ko.mdcontent/self-host/rustdesk-server-pro/ldap/_index.ko.mdcontent/self-host/rustdesk-server-pro/license/_index.ko.mdcontent/self-host/rustdesk-server-pro/oidc/_index.ko.mdcontent/self-host/rustdesk-server-pro/oidc/azure/_index.ko.mdcontent/self-host/rustdesk-server-pro/permissions/_index.ko.mdcontent/self-host/rustdesk-server-pro/relay/_index.ko.mdcontent/self-host/rustdesk-server-pro/smtp/_index.ko.mdcontent/self-host/rustdesk-server-pro/smtp/microsoft-365/_index.ko.mdcontent/self-host/rustdesk-server-pro/strategy/_index.ko.mdcontent/videos/_index.ko.mdhugo.yaml
| ```sh | ||
| # For Ubuntu | ||
| sudo yum install libfuse2 | ||
| ./rustdesk-<version>.AppImage | ||
| ``` |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
printf '\n== Relevant local file context ==\n'
sed -n '60,90p' content/client/linux/_index.ko.md
printf '\n== Search for related package-manager commands ==\n'
rg -n "yum install libfuse2|apt install libfuse2|libfuse2|AppImage" content/client/linux -S
printf '\n== Search for upstream-reference clues in repo ==\n'
rg -n "rustdesk.com/docs/en/client/linux|client/linux" -S .Repository: rustdesk/doc.rustdesk.com
Length of output: 5248
🌐 Web query:
RustDesk Linux docs AppImage libfuse2 Ubuntu yum install
💡 Result:
To run a RustDesk AppImage on modern Ubuntu systems, you often need to install the libfuse2 library because AppImages rely on FUSE 2, which is not installed by default in newer Ubuntu versions [1][2][3]. For Ubuntu 22.04 and later, the installation command depends on your specific version [3][4]: For Ubuntu 22.04: sudo apt install libfuse2 [1][2][4] For Ubuntu 24.04 and newer: sudo apt install libfuse2t64 [1][3][4] Note: Do not install the package named simply "fuse" or "fuse3" to fix this, as it may cause system instability [2][3][4]. Regarding "yum install": The command sudo yum install libfuse2 is generally applicable to Red Hat-based distributions (like Fedora or CentOS) to provide the necessary FUSE 2 support for AppImages [5]. For installing the RustDesk application itself on these systems, the recommended method is to use the RPM package via sudo yum localinstall ./rustdesk-<version>.rpm [6][7]. On Debian-based distributions like Ubuntu, the primary method for installing RustDesk is to use the DEB package via sudo apt install -fy ./rustdesk-<version>.deb rather than the AppImage [8][6][7]. Using the package manager ensures better system integration and easier updates [8].
Citations:
- 1: https://docs.appimage.org/user-guide/troubleshooting/fuse.html
- 2: https://askubuntu.com/questions/1403811/appimage-on-ubuntu-22-04
- 3: https://www.omgubuntu.co.uk/2023/04/appimages-libfuse2-ubuntu-23-04
- 4: https://itsfoss.com/appimage-fuse-issue/
- 5: https://rustdesk.com/docs/en/client/linux/
- 6: https://github.com/rustdesk/doc.rustdesk.com/blob/6af6ba30/content/client/_index.en.md
- 7: https://github.com/JohnnyElaine/RustDeskSetup
- 8: https://idroot.us/install-rustdesk-linux-mint-22/
Use Ubuntu’s package manager for the AppImage prerequisite. yum install libfuse2 is the Fedora/RHEL path; Ubuntu should use apt install libfuse2 (or libfuse2t64 on 24.04+).
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@content/client/linux/_index.ko.md` around lines 71 - 75, The Ubuntu AppImage
prerequisite command is using the wrong package manager, so update the Linux
client docs snippet to use Ubuntu’s apt-based install path instead of yum. In
the AppImage setup section of the Ubuntu instructions, replace the Fedora/RHEL
reference with the correct Ubuntu package name and note the 24.04+ variant if
needed. Keep the surrounding AppImage launch step unchanged.
Source: MCP tools
| 또는 RMM, Intune 등과 함께 대량 배포 스크립트를 사용할 수도 있습니다. ID와 비밀번호는 스크립트에서 출력됩니다. 이를 수집하거나 ID와 비밀번호를 각각 다른 스크립트로 분리하여 수집해야 합니다. | ||
|
|
||
| 영구 비밀번호는 `rustdesk_pw` 이후 `()` 내부의 내용을 PowerShell용 선호하는 비밀번호로 변경하고, 기타 플랫폼의 경우 해당 라인을 변경함으로써 무작위에서 원하는 비밀번호로 변경할 수 있습니다. |
There was a problem hiding this comment.
🔒 Security & Privacy | 🟠 Major | ⚡ Quick win
Don't print the generated password to stdout.
These examples are aimed at managed rollout tooling, so stdout is usually captured into logs. Emitting the unattended-access password here turns the script into a credential leak; keep it local/secret-only instead.
Also applies to: 150-155, 198-203, 274-283, 377-386
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@content/self-host/client-deployment/_index.ko.md` around lines 35 - 37, The
deployment-script examples in the client deployment docs currently tell users to
print the generated unattended-access password to stdout, which should be
avoided for managed rollout tooling. Update the relevant examples in the
document to keep the password local/secret-only instead of emitting it, and
adjust the surrounding text near the affected deployment sections so it no
longer instructs users to capture the password from script output.
| ## 스크립트로 설치했는데, 서비스를 시작하고 중지하려면 어떻게 해야 하나요? | ||
| 서비스는 systemd를 사용하므로 `sudo systemctl stop|start|restart rustdesk-hbbs|rustdesk-hbbr`를 이용해 시작하고 중지할 수 있습니다. 예: `sudo systemctl restart rustdesk-hbbs`. | ||
|
|
||
| ## 스크립트로 설치했는데, Linux 로그를 어떻게 볼 수 있나요? | ||
| 로그는 `/var/log/rustdesk-server`에 저장되어 있으며, `tail /var/log/rustdesk-server/hbbs.log` 또는 `tail /var/log/rustdesk-server/hbbs.error`를 사용하여 확인할 수 있습니다. | ||
|
|
||
| ## 스크립트로 설치했는데 RustDesk 서비스의 상태를 어떻게 확인할 수 있나요? | ||
| `sudo systemctl status rustdesk-hbbs|rustdesk-hbbr`, 예를 들어 `sudo systemctl status rustdesk-hbbs`와 같은 상태를 확인하려면. |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
Fix the systemd examples.
| is a shell pipeline here, so the commands won't do what the prose says. Split them into separate systemctl invocations for rustdesk-hbbs and rustdesk-hbbr.
Example
- sudo systemctl stop|start|restart rustdesk-hbbs|rustdesk-hbbr
+ sudo systemctl stop rustdesk-hbbs
+ sudo systemctl stop rustdesk-hbbr
+ sudo systemctl start rustdesk-hbbs
+ sudo systemctl start rustdesk-hbbr
+ sudo systemctl restart rustdesk-hbbs
+ sudo systemctl restart rustdesk-hbbr📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ## 스크립트로 설치했는데, 서비스를 시작하고 중지하려면 어떻게 해야 하나요? | |
| 서비스는 systemd를 사용하므로 `sudo systemctl stop|start|restart rustdesk-hbbs|rustdesk-hbbr`를 이용해 시작하고 중지할 수 있습니다. 예: `sudo systemctl restart rustdesk-hbbs`. | |
| ## 스크립트로 설치했는데, Linux 로그를 어떻게 볼 수 있나요? | |
| 로그는 `/var/log/rustdesk-server`에 저장되어 있으며, `tail /var/log/rustdesk-server/hbbs.log` 또는 `tail /var/log/rustdesk-server/hbbs.error`를 사용하여 확인할 수 있습니다. | |
| ## 스크립트로 설치했는데 RustDesk 서비스의 상태를 어떻게 확인할 수 있나요? | |
| `sudo systemctl status rustdesk-hbbs|rustdesk-hbbr`, 예를 들어 `sudo systemctl status rustdesk-hbbs`와 같은 상태를 확인하려면. | |
| ## 스크립트로 설치했는데, 서비스를 시작하고 중지하려면 어떻게 해야 하나요? | |
| 서비스는 systemd를 사용하므로 다음 명령으로 시작하고 중지할 수 있습니다. | |
| `sudo systemctl stop rustdesk-hbbs` | |
| `sudo systemctl stop rustdesk-hbbr` | |
| `sudo systemctl start rustdesk-hbbs` | |
| `sudo systemctl start rustdesk-hbbr` | |
| `sudo systemctl restart rustdesk-hbbs` | |
| `sudo systemctl restart rustdesk-hbbr` | |
| ## 스크립트로 설치했는데, Linux 로그를 어떻게 볼 수 있나요? | |
| 로그는 `/var/log/rustdesk-server`에 저장되어 있으며, `tail /var/log/rustdesk-server/hbbs.log` 또는 `tail /var/log/rustdesk-server/hbbs.error`를 사용하여 확인할 수 있습니다. | |
| ## 스크립트로 설치했는데 RustDesk 서비스의 상태를 어떻게 확인할 수 있나요? | |
| `sudo systemctl status rustdesk-hbbs|rustdesk-hbbr`, 예를 들어 `sudo systemctl status rustdesk-hbbs`와 같은 상태를 확인하려면. |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@content/self-host/rustdesk-server-pro/faq/_index.ko.md` around lines 129 -
136, The systemd examples in the FAQ use a pipeline character that makes the
commands incorrect. Update the examples in the relevant FAQ entries so each
`systemctl` action is shown as separate invocations for `rustdesk-hbbs` and
`rustdesk-hbbr` instead of `rustdesk-hbbs|rustdesk-hbbr`, and keep the
surrounding text in the same section consistent with the corrected command
usage.
| ## PowerShell을 사용하여 RustDesk를 업데이트하려면 어떻게 해야 하나요? | ||
|
|
||
| ```ps | ||
| $ErrorActionPreference= 'silentlycontinue' | ||
|
|
||
| $rdver = ((Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\RustDesk\").Version) | ||
|
|
||
| if ($rdver -eq "1.2.6") | ||
| { | ||
| Write-Output "RustDesk $rdver is the newest version." | ||
| Exit | ||
| } | ||
|
|
||
| if (!(Test-Path C:\Temp)) | ||
| { | ||
| New-Item -ItemType Directory -Force -Path C:\Temp > null | ||
| } | ||
|
|
||
| cd C:\Temp | ||
|
|
||
| Invoke-WebRequest "https://github.com/rustdesk/rustdesk/releases/download/1.2.6/rustdesk-1.2.6-x86_64.exe" -Outfile "rustdesk.exe" | ||
| Start-Process .\rustdesk.exe --silent-install -wait | ||
| ``` |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
Don't hard-code 1.2.6 in the updater.
This snippet always downloads RustDesk 1.2.6, so readers following the FAQ will install an obsolete build instead of updating. Please make the release source/version dynamic or replace this with a current updater flow.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@content/self-host/rustdesk-server-pro/faq/_index.ko.md` around lines 215 -
237, The PowerShell updater snippet is hard-coding RustDesk version 1.2.6, which
makes the FAQ install an outdated build. Update the update flow in this section
to avoid embedding a fixed release number in the $rdver check and
Invoke-WebRequest URL, and instead use a dynamic/current release source or
replace the example with a maintained updater approach so the script always
fetches the latest supported version.
| 설치하기 시 `Waiting for RustDesk Relay service to become active...`가 나타나는 경우, 이는 SELinux로 인해 발생할 수 있습니다. 다음 명령어를 시도해 볼 수 있습니다: | ||
|
|
||
| ```sh | ||
| sudo semanage fcontext -a -t NetworkManager_dispatcher_exec_t 'hbbs' | ||
| sudo semanage fcontext -a -t NetworkManager_dispatcher_exec_t 'hbbr' | ||
| sudo restorecon -v '/usr/bin/hbbs' | ||
| sudo restorecon -v '/usr/bin/hbbr' | ||
| ``` |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
Point the SELinux rule at the installed binaries. semanage fcontext expects a path regex, so bare hbbs/hbbr won’t match /usr/bin/hbbs or /usr/bin/hbbr; update both entries to the full install paths here.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@content/self-host/rustdesk-server-pro/faq/_index.ko.md` around lines 504 -
511, The SELinux guidance in the FAQ uses bare binary names in the semanage
fcontext commands, which won’t match the installed executables. Update the
SELinux rule examples in the RustDesk Relay section to use the full install
paths for both hbbs and hbbr, and keep the restorecon examples aligned with
those same installed binary paths.
|
Fixed the translation issues from the review:
A few flagged items match the English source (e.g. yum install libfuse2, port 443 label, example IP), so I kept ko consistent with it. |
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
content/self-host/rustdesk-server-pro/faq/_index.ko.md (1)
24-34: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick winKeep the install-script link in the Korean locale.
Line 28 still sends readers to the English docs, even though this PR adds the Korean installscript page. Point it at the localized page instead so the setup flow stays in
/docs/ko/.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@content/self-host/rustdesk-server-pro/faq/_index.ko.md` around lines 24 - 34, The install-script link in the Korean FAQ still points to the English docs, so update the existing markdown link in the install steps to the localized installscript page under the Korean docs path. Keep the change within the FAQ entry in _index.ko.md and make sure the referenced install flow stays in /docs/ko/ rather than routing through the English URL.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Outside diff comments:
In `@content/self-host/rustdesk-server-pro/faq/_index.ko.md`:
- Around line 24-34: The install-script link in the Korean FAQ still points to
the English docs, so update the existing markdown link in the install steps to
the localized installscript page under the Korean docs path. Keep the change
within the FAQ entry in _index.ko.md and make sure the referenced install flow
stays in /docs/ko/ rather than routing through the English URL.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 04406230-122d-4d7c-ad1e-9deef2ced0d9
📒 Files selected for processing (18)
content/client/_index.ko.mdcontent/self-host/_index.ko.mdcontent/self-host/client-configuration/_index.ko.mdcontent/self-host/client-configuration/advanced-settings/_index.ko.mdcontent/self-host/client-deployment/_index.ko.mdcontent/self-host/rustdesk-server-oss/_index.ko.mdcontent/self-host/rustdesk-server-oss/install/_index.ko.mdcontent/self-host/rustdesk-server-oss/synology/dsm-6/_index.ko.mdcontent/self-host/rustdesk-server-pro/_index.ko.mdcontent/self-host/rustdesk-server-pro/console/_index.ko.mdcontent/self-host/rustdesk-server-pro/faq/_index.ko.mdcontent/self-host/rustdesk-server-pro/installscript/Docker/_index.ko.mdcontent/self-host/rustdesk-server-pro/installscript/Script/_index.ko.mdcontent/self-host/rustdesk-server-pro/installscript/_index.ko.mdcontent/self-host/rustdesk-server-pro/installscript/windows/_index.ko.mdcontent/self-host/rustdesk-server-pro/license/_index.ko.mdcontent/self-host/rustdesk-server-pro/relay/_index.ko.mdcontent/self-host/rustdesk-server-pro/smtp/microsoft-365/_index.ko.md
✅ Files skipped from review due to trivial changes (11)
- content/self-host/_index.ko.md
- content/self-host/rustdesk-server-pro/installscript/_index.ko.md
- content/self-host/rustdesk-server-oss/synology/dsm-6/_index.ko.md
- content/self-host/rustdesk-server-oss/install/_index.ko.md
- content/self-host/rustdesk-server-oss/_index.ko.md
- content/self-host/rustdesk-server-pro/license/_index.ko.md
- content/self-host/rustdesk-server-pro/installscript/Script/_index.ko.md
- content/self-host/rustdesk-server-pro/installscript/Docker/_index.ko.md
- content/client/_index.ko.md
- content/self-host/rustdesk-server-pro/installscript/windows/_index.ko.md
- content/self-host/rustdesk-server-pro/console/_index.ko.md
🚧 Files skipped from review as they are similar to previous changes (4)
- content/self-host/client-deployment/_index.ko.md
- content/self-host/rustdesk-server-pro/smtp/microsoft-365/_index.ko.md
- content/self-host/rustdesk-server-pro/relay/_index.ko.md
- content/self-host/client-configuration/advanced-settings/_index.ko.md
Summary
Adds a complete Korean (
ko) locale for the documentation — all 46 pages translated from the English source, plus thekolanguage registration inhugo.yaml.Scope
Commits are split by section so they can be reviewed independently:
add Korean language config—koblock inhugo.yaml(mirrors thejablock)translate client, videos, home— landing page + RustDesk Client + video tutorialstranslate self-host (OSS, config, deployment)— OSS server, client configuration, deployment, NATtranslate rustdesk-server-pro— Pro server (console, admin/control roles, SMTP, OIDC, LDAP, license, etc.)translate dev/build docs— build instructions per platformTranslation notes
src/lang/ko.rsin the main repo) so the docs match what users see in the app (e.g. 릴레이 서버 / relay server, 주소록 / address book). Product names, protocol acronyms (NAT, TLS, OIDC, SMTP, …), Docker, and configuration keys are kept in English.Build
Builds cleanly with the CI Hugo version (
0.147.8 extended), 0 errors.korenders 99 pages, matching the other complete locales.I'm happy to adjust terminology or wording based on maintainer preference.
Summary by CodeRabbit