jiayuasu opened a new pull request, #2935:
URL: https://github.com/apache/sedona/pull/2935

   ## Did you read the Contributor Guide?
   
   - Yes, I have read the [Contributor 
Rules](https://sedona.apache.org/latest/community/rule/) and [Contributor 
Development Guide](https://sedona.apache.org/latest/community/develop/)
   
   ## Is this PR related to a ticket?
   
   - Yes, and the PR name follows the format `[GH-XXX] my subject`. Closes 
#2911 (Phase 4 of EPIC #2867). Final PR in the Phase 4 series — follows up on 
#2931, #2933, #2934.
   
   ## What changes were proposed in this PR?
   
   Phase 4d of the Chinese-documentation EPIC (#2867). Translates the final 2 
tutorial pages, completing Phase 4.
   
   **Translated in this PR:**
   
   - `tutorial/rdd.md` (871 lines)
   - `tutorial/sql.md` (1,438 lines — the largest single tutorial page)
   
   After this PR merges, **all 27 tutorial pages** have Chinese versions on the 
docs site. Phase 4 of #2867 is complete.
   
   Code blocks, command snippets, version macros (`{{ sedona.current_version 
}}`, `{{ sedona.current_geotools }}`), admonitions, and inline tab attributes 
(`=== "Scala"`, etc.) are preserved verbatim. Only prose, headings, table 
headers, and explanatory inline comments are translated.
   
   ## How was this patch tested?
   
   Built the docs locally with `uv sync --group docs && uv run mkdocs build` 
and verified:
   
   - The build succeeds.
   - The 2 new `*.zh.md` files render under `/zh/tutorial/`.
   - `pre-commit run --all-files` passes (license headers auto-added by 
`insert-license`, re-staged before commit).
   
   ## Did this PR include necessary documentation updates?
   
   - Yes, this PR is itself a documentation translation. Phase 4 (Tutorial / 
Programming Guide) is now complete — subsequent phases (#2912-#2919) translate 
other doc sections.


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

Reply via email to