morningman opened a new pull request, #4213:
URL: https://github.com/apache/doris-website/pull/4213

   ## Scope
   
   Start T09-DEV-001 with its first reviewable sub-batch: the Dev quick-start 
guide (1 of 20 assigned pages). The remaining 19 pages stay in T09-DEV-001. 
This split keeps the initial long MDX translation focused for Japanese 
proofreading.
   
   The Dev and 4.x English documents have the same native doc ID, relative 
path, and normalized source SHA-256 
(`c1f1c82c39f02f2368e4f214b72a7be258983de46fcb04615078a1dd8d35a60b`) at master 
`de6b50dd09`. This PR changes only Dev. The separate 4.x batch can reuse the 
reviewed text and must carry its own state record and checks.
   
   ## Changes
   
   - Translate the prose and metadata of `getting-started/quick-start.mdx` into 
Japanese.
   - Record the exact English source and Japanese target hashes with 
`reviewStatus: machine`. Human Japanese proofreading is still pending.
   - Preserve SQL, shell commands, links, numbers, MDX structure, and source 
heading anchors.
   
   ## Verification
   
   - Translation gate: 1 changed page checked, 0 errors.
   - Dev scope en/zh-CN/ja build: success with `DORIS_ENABLE_JA=true 
DOCS_VERSIONS=current`.
   - Japanese static verification: 1,778 non-draft pages checked, 0 errors.
   - New Dev page renders Japanese body and Japanese canonical. Adjacent 
untranslated Dev page retains English body, English canonical, and `noindex, 
follow`.
   - `build-scope.cjs` selects current/ja; no full-version build required.
   
   ## Review needed before merge
   
   Please have a Japanese reviewer proofread the prose and confirm technical 
meaning against the Dev English source. The state record remains 
machine-reviewed until that review is complete. This PR should remain a draft 
until then.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to