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

   ## Summary
   
   - Translate five 4.x `JSON_EXTRACT_*` function pages into Japanese: DOUBLE, 
INT, ISNULL, LARGEINT, and STRING.
   - Add source-bound Japanese translation state for each page with machine 
review status. No human Japanese proofreading is claimed.
   - Preserve the English source SQL, expected outputs, links, numbers, and 
heading structure. The five 4.x sources are byte-identical to their current Dev 
counterparts, but no merged Dev Japanese target exists for these pages.
   
   This is sub-batch `T09-4X-052b` from the existing 20-page JSON function 
inventory. It adds no English source, site logic, build script, sidebar, or 
route changes. The remaining eight inventory pages stay in later batches.
   
   ## Validation
   
   - `node scripts/i18n/check-translations.cjs --base 
8bad9a9a9922364e218c73aab145b521fd884334`: 5 checked, 0 errors.
   - `node scripts/i18n/audit-coverage.cjs --source-ref HEAD --output 
.i18n-build/t09/after-052b.json`: 4.x current 6 on this branch versus 1 on 
merged master; total current 238 versus 233. This PR contributes five candidate 
pages and is not counted as merged coverage yet.
   - `git diff --check 8bad9a9a9922364e218c73aab145b521fd884334...HEAD`: clean.
   - Verified all five source/target hashes, protected structure, exact fenced 
SQL and output blocks, and five relative links to existing 4.x English targets.
   
   As previously agreed for translation-only batches, no local site build was 
run. The PR Build Check will validate the site build.
   


-- 
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