Skip to content

Improve Japanese and Simplified Chinese documentation quality #279

Closed

Description

@abruption

Background

Improve the Japanese and Simplified Chinese documentation so it reads naturally and consistently, while preserving the meaning of the English canonical documents. The recently improved Korean documentation may serve as a style reference, but the English source remains authoritative for meaning.

Scope

Only these eight files in this repository:

  • Japanese: README.ja.md, RELEASING.ja.md, SECURITY.ja.md, plugins/session-peer/README.ja.md
  • Simplified Chinese: README.zh-CN.md, RELEASING.zh-CN.md, SECURITY.zh-CN.md, plugins/session-peer/README.zh-CN.md

For both root localized README files, center the title, badges, language selector, and short introduction inside <div align="center">, closing the wrapper before the body.

Acceptance criteria

  • Improve natural phrasing and consistency of terminology and style across each language.
  • Verify against the English canonical documents that feature descriptions, installation scope, versions and numbers, commands and flags, identifiers and placeholders, code examples, security limitations, release evidence, and operational boundaries retain their meaning.
  • Preserve Markdown structure, code blocks, links, and anchors; pass the local documentation checks and CI.
  • Do not change the Korean documentation, English canonical documents, runtime code, or operational settings.

This issue covers Japanese and Simplified Chinese documentation quality only. It does not change the scope of the existing Korean translation issue or PR.

Activity

  1. abruption commented on Oct 7, 2026

    @abruption
    OwnerAuthor

    추가 수락 조건: 이 이슈의 루트 현지화 README(README.ja.md, README.zh-CN.md)는 제목·배지·언어 선택기·짧은 소개를 <div align="center">로 감싸고, 본문 시작 전에 닫습니다. 기존 한국어 PR #278과 영어 정본은 별도 범위로 유지합니다.

  2. changed the title [-]문서(일본어·중국어 간체): 번역 품질 개선[/-] [+]Improve Japanese and Simplified Chinese documentation quality[/+] on Oct 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions