jiayuasu opened a new pull request, #2937: URL: https://github.com/apache/sedona/pull/2937
## 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 #2912, part of EPIC #2867. ## What changes were proposed in this PR? Phase 5 of the Chinese-documentation EPIC (#2867). Adds Chinese (`zh`) translations for the Community and Apache Software Foundation pages so `/zh/community/` and `/zh/asf/` render in Chinese. **Translated in this PR (12 files):** - `asf/`: `asf`, `telemetry` - `community/`: `contact`, `publication`, `snapshot`, `rule`, `geopandas`, `vote`, `release-manager`, `develop`, `contributor`, `publish` ASF-mandated wording (trademark notice in `asf.md`, license-related text) is preserved verbatim. Email templates inside `release-manager.md`, `contributor.md`, and `publish.md` are kept in English on purpose — these are the actual emails sent to ASF mailing lists, and translating them would mislead readers about what to send. Bash scripts, Maven commands, and version macros (`{{ sedona_create_release.* }}`) are unchanged; only the prose around them is translated. ## How was this patch tested? Built the docs locally with `uv sync --group docs && uv run mkdocs build` and verified: - The build succeeds with no new warnings introduced by Phase 5. - The 12 new `*.zh.md` files render under `/zh/community/` and `/zh/asf/`. - `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. Subsequent phases (#2913-#2919) translate the remaining 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]
