morningman opened a new pull request, #4238: URL: https://github.com/apache/doris-website/pull/4238
## Summary Translate all 20 pages in the original `T09-4X-053` batch for Japanese Doris 4.x: JSON, VARIANT, and IP scalar functions. Add source and target hashes to the Japanese translation state with `reviewStatus=machine`. Also fix two 4.x English source issues found while translating: - Render the `JSON_SEARCH` return-value cases as a Markdown list instead of an indented code block. - Use the documented `<json>` parameter name in the `JSON_TYPE` NULL note. The two source records point to the source-fix commit `5e97039b57ee4ebe9dd963a66cf70e1c9c9d4939`. After squash merge, a follow-up state-only PR must replace their `sourceCommit` with the merge commit SHA. ## Validation - `node scripts/i18n/check-translations.cjs --base 8bad9a9a9922364e218c73aab145b521fd884334`: 20 checked, 0 errors. - `node scripts/i18n/audit-coverage.cjs --source-ref HEAD`: 4.x current coverage 21, pending 1,576 on this branch. Master coverage remains 233 overall until merge. - Protected code, SQL, output, links, headings, and metadata: 20/20 matched the current 4.x English source. - Eight relative links and one anchor resolve; all 20 front matter blocks have Japanese language and descriptions. - `git diff --check` reports source-inherited whitespace in SQL/output blocks, two source-inherited trailing blank lines, and source-matched Markdown hard line breaks. No translated prose has unintentional trailing whitespace. Per the Japanese i18n batch rules, no local site build was run for this content-only translation. The PR Build Check will validate the site build. ## Source limitations `JSON_PARSE_ERROR_TO_VALUE` has only a brief description in the English source, so its Japanese page translates that text without inventing behavior. The `TO_JSON` DATE conversion narrative and examples appear inconsistent and need a separate behavior check before changing the source. -- 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]
