[GH-2867] Translate Stats, Viz, and SQL overview pages to Chinese#2947
Merged
jiayuasu merged 1 commit intoMay 11, 2026
Merged
Conversation
Bundles three sub-phases of the docs i18n EPIC: - Phase 6 (apache#2913) — Stats & Viz API reference: docs/api/stats/sql, docs/api/viz/sql, docs/api/viz/java-api - Phase 7 (apache#2914) — SQL API overview & concepts: Overview, Optimizer, NearestNeighbourSearching, CRS-Transformation, Parameter, DataFrameAPI, Visualization-SedonaPyDeck, Visualization-SedonaKepler, Reading-legacy-parquet, Spider - Phase 9 (apache#2916) — SQL Raster concept pages: Raster-map-algebra, Raster-affine-transformation The pure function reference pages (Geometry-Functions.md, Raster-Functions.md, and per-function detail files under api/sql/) are intentionally left in English: they are dominated by function signatures, parameter tables, and code, where the English source is the canonical spec and translation churn outweighs the readability benefit.
This was referenced May 11, 2026
jiayuasu
added a commit
that referenced
this pull request
May 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Did you read the Contributor Guide?
Is this PR related to a ticket?
[GH-XXX] my subject. Part of EPIC Add Chinese version of the documentation #2867.Bundles three sub-phases (small enough to review together): closes #2913, closes #2914, closes #2916.
What changes were proposed in this PR?
Adds Simplified Chinese (
*.zh.md) translations for the docs site, covering the Stats/Viz API entry pages and the SQL API overview/concept pages:Phase 6 (#2913) — Stats & Viz reference (3 files):
docs/api/stats/sql.mddocs/api/viz/sql.mddocs/api/viz/java-api.mdPhase 7 (#2914) — SQL API overview & concepts (10 files):
Overview.md,Optimizer.md,NearestNeighbourSearching.md,CRS-Transformation.md,Parameter.md,DataFrameAPI.md,Visualization-SedonaPyDeck.md,Visualization-SedonaKepler.md,Reading-legacy-parquet.md,Spider.mdPhase 9 (#2916) — SQL Raster concept pages (2 files):
Raster-map-algebra.md,Raster-affine-transformation.md15 new files; no existing files modified; no nav changes (the labels were translated centrally in
mkdocs.ymlin earlier phases).Intentionally left in English
The pure function reference pages —
docs/api/sql/Geometry-Functions.md,docs/api/sql/Raster-Functions.md, and the per-function detail files underdocs/api/sql/Geometry-*/,docs/api/sql/Raster-*/,docs/api/flink/,docs/api/snowflake/— are intentionally left in English. They are dominated by function signatures, parameter tables, return types, and code blocks, where the English source is the canonical spec; translating the surrounding prose adds little value vs. the maintenance overhead. Follow-up sub-issues #2915 / #2917 / #2918 will be closed with this rationale.How was this patch tested?
.zh.mdhas the ASF license header at the top (pre-commitinsert-licensehook passes); all markdown links, code blocks, function names, and table cells containing code/identifiers are preserved verbatim from the English source.docs/setup/overview.zh.md,docs/tutorial/sql.zh.md,docs/community/develop.zh.md.Did this PR include necessary documentation updates?