RustDesk Server Pro Chinese Translation Issues Report

Executive Summary

After analyzing all Chinese translation files (zh-cn and zh-tw) in the rustdesk-server-pro directory, I’ve identified significant translation issues that need to be addressed. The main issues include:

  1. Extensive untranslated English content in both zh-cn and zh-tw files
  2. Structural mismatches between English and Chinese versions
  3. Technical terms left in English (some intentionally, but many that should be translated)

Key Findings

1. Files with Major Translation Issues

installscript/_index.en.md

  • Untranslated content: 17 instances in zh-cn, 17 instances in zh-tw
  • Example issues:
    • “For more details, please check Docker” - completely untranslated
    • “If you are proficient in Linux, please use the script below. Otherwise, you may encounter significant issues if it fails, and it could be difficult to determine why it isn’t working.” - entire paragraph left in English
    • “Convert from open source” - section header untranslated
    • Entire paragraphs about Docker conversion process remain in English

faq/_index.en.md

  • Untranslated content: 48 instances in zh-cn, 44 instances in zh-tw
  • Structural issues:
    • zh-cn: Section count mismatch (EN: 40, ZH: 49) and code block mismatch (EN: 18, ZH: 21)
  • Example issues:
    • Docker command outputs left untranslated (e.g., “seconds ago Restarting”)
    • PowerShell script comments in English
    • Linux commands and their descriptions partially translated
    • Nginx configuration comments “managed by Certbot” left in English

installscript/windows/_index.en.md

  • Untranslated content: 5 instances each in zh-cn and zh-tw
  • Example issues:
    • “Dynamic Content Compression” - technical term left untranslated
    • “Application Request Routing” - repeated multiple times without translation

relay/_index.en.md

  • Untranslated content: 8 instances each in zh-cn and zh-tw
  • Structural issues: Section count mismatches in both versions
  • Example issues:
    • Command outputs and log messages untranslated
    • “Your Access Key” placeholder text not localized

2. Common Patterns of Untranslated Content

  1. Technical Documentation: Commands, configuration files, and code snippets often have English comments or descriptions
  2. UI Elements: Button names, menu items, and interface elements sometimes remain in English
  3. Error Messages: System messages and error outputs frequently untranslated
  4. Placeholder Text: Template variables like “Your Access Key” not localized

3. Structural Inconsistencies

Several files show mismatches in:

  • Number of sections between English and Chinese versions
  • Code block counts
  • List item counts

This suggests content may have been added to English versions without corresponding updates to translations.

Recommendations

Immediate Actions Needed

  1. Complete Translation of installscript/_index files

    • These contain critical installation instructions that users need to understand
    • Priority: HIGH

  2. Update FAQ translations

    • The FAQ has the most untranslated content and structural issues
    • Consider breaking this into smaller tasks due to volume
    • Priority: HIGH

  3. Standardize Technical Terms

    • Create a glossary of technical terms that should remain in English vs. those that should be translated
    • Examples needing decision: “Dynamic Content Compression”, “Application Request Routing”

Process Improvements

  1. Implement Translation Tracking

    • Use the analysis script regularly to catch new untranslated content
    • Set up automated checks before releases

  2. Maintain Structural Consistency

    • When updating English docs, create corresponding tickets for Chinese translations
    • Include section counts and structure validation in review process

  3. Context-Aware Translation

    • Provide translators with full context for technical content
    • Include screenshots or examples where applicable

Technical Details

Total issues found across all files:

  • Untranslated text instances: 152
  • Structural mismatches: 5
  • Files affected: 6 major documentation files

The complete JSON analysis is available at: /Users/hzhou/doc.rustdesk.com/content/self-host/rustdesk-server-pro/translation_analysis_results.json

Next Steps

  1. Prioritize translation of the installscript and FAQ sections
  2. Review and update the Windows installation guide translations
  3. Establish a regular review cycle for translation completeness
  4. Consider using translation memory tools to maintain consistency