Translations update from OSGeo Weblate #141
Conversation
📝 WalkthroughWalkthroughThis pull request updates numerous Spanish localization files for the PostGIS documentation. The changes include adjustments to metadata—such as PO revision dates, translator credits, language team URLs, and pluralization rules—standardizing them to the new information for 2025. In addition, many translation entries for commands, functions, and instructional texts have been added or refined to improve clarity and accuracy for Spanish-speaking users. Changes
Possibly related PRs
Poem
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🧹 Nitpick comments (8)
postgis-intro/sources/locale/es/LC_MESSAGES/backup.po (1)
68-483: Consider continuing translation for remaining content.There are still many untranslated sections in this file (empty msgstr entries). While this PR provides valuable translations for the initial sections, it would be beneficial to continue the translation effort for the remaining content in future contributions.
postgis-intro/sources/locale/es/LC_MESSAGES/equality.po (3)
47-47: Consider following Spanish title capitalization conventionIn Spanish, titles typically only capitalize the first word. Consider changing "Exactamente igual" to "Exactamente Igual" or keep it lowercase depending on the style guide for this documentation.
77-77: Consider following Spanish title capitalization conventionIn Spanish, titles typically only capitalize the first word. Consider changing "Espacialmente igual" to "Espacialmente Igual" or keep it lowercase depending on the style guide for this documentation.
109-109: Consider following Spanish title capitalization conventionIn Spanish, titles typically only capitalize the first word. Consider changing "Límites iguales" to "Límites Iguales" or keep it lowercase depending on the style guide for this documentation.
postgis-intro/sources/locale/es/LC_MESSAGES/spatial_relationships_exercises.po (1)
67-68: Consider keeping function name in original form.While the description translation is accurate, the function name has been translated from
ST_DistancetoST_Distancia. Function names are typically not translated in programming contexts as users will need to use the original English function name in their SQL queries.-:command:`ST_Distancia(geometría A, geometría B)` devuelve la distancia mínima entre la geometría A y la geometría B" +:command:`ST_Distance(geometría A, geometría B)` devuelve la distancia mínima entre la geometría A y la geometría B"postgis-intro/sources/locale/es/LC_MESSAGES/joins_exercises.po (2)
87-109: Consider completing the remaining translations.Several PostGIS functions remain untranslated in this file, including
ST_GeomFromText,ST_Intersects,ST_Length,ST_Touches, andST_Within. Since other functions have been translated, consider completing these translations for consistency.
111-178: Missing translations for table descriptions and exercises.The table descriptions and exercise questions remain untranslated. Consider translating these sections to provide a complete Spanish language experience for users.
postgis-intro/sources/locale/es/LC_MESSAGES/simple_sql_exercises.po (1)
180-208: Fix inconsistent question formatting.Some translated questions are missing closing quotation marks or question marks. Ensure all questions follow the same formatting pattern for consistency.
-msgstr "**¿Cuántos registros hay en la tabla nyc_streets?**" +msgstr "**¿Cuántos registros hay en la tabla nyc_streets?**" -msgstr "**¿Cuántas calles de Nueva York empiezan por \"B\"?" +msgstr "**¿Cuántas calles de Nueva York empiezan por \"B\"?**" -msgstr "**¿Cuál es la población de la ciudad de Nueva York?" +msgstr "**¿Cuál es la población de la ciudad de Nueva York?**" -msgstr "**¿Cuál es la población del Bronx?" +msgstr "**¿Cuál es la población del Bronx?**" -msgstr "**¿Cuántos barrios hay en cada distrito?" +msgstr "**¿Cuántos barrios hay en cada distrito?**"
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (19)
postgis-intro/sources/locale/es/LC_MESSAGES/3d.po(1 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/about_data.po(1 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/backup.po(1 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/creating_db.po(5 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/equality.po(7 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/geography_exercises.po(1 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/geometries.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/geometries_exercises.po(3 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/geometry_returning.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/geometry_returning_exercises.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/joins.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/joins_advanced.po(1 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/joins_exercises.po(1 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/license.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/projection_exercises.po(3 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/schemas.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/simple_sql.po(7 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/simple_sql_exercises.po(8 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/spatial_relationships_exercises.po(2 hunks)
🔇 Additional comments (70)
postgis-intro/sources/locale/es/LC_MESSAGES/license.po (4)
7-7: Translator credit added appropriately.A new translator credit has been added for Paulo Cesar, which properly attributes his contributions to the Spanish translation.
13-14: Updated metadata with new translator information.The PO-Revision-Date and Last-Translator fields have been properly updated to reflect the most recent changes made by Paulo Cesar.
Note: The revision date is set to 2025-03-14, which appears to be in the future. This may be intentional for planning purposes, but you might want to verify this is the intended date.
22-22: Updated Weblate version.The X-Generator field has been updated to reflect the current version of Weblate (5.4.3) used for this translation.
47-48: New translation added for attribution requirement.This adds a previously missing Spanish translation for the attribution requirement text. The translation accurately conveys the meaning of the English original and uses appropriate Spanish terminology.
postgis-intro/sources/locale/es/LC_MESSAGES/backup.po (5)
6-6: Translator information updated appropriately.The file now properly credits Paulo Cesar as the translator with the correct email and year (2025).
12-16: Metadata fields updated correctly.The revision date, translator information, language team URL, and language code have been properly updated. These changes ensure proper attribution and tracking of the translation work.
20-21: Spanish pluralization rules and generator information added.The addition of proper pluralization rules for Spanish and the Weblate generator information enhance the metadata completeness.
26-26: Good translation of the title.The Spanish translation "Copia de seguridad y restauración de PostgreSQL" accurately captures the meaning of "PostgreSQL Backup and Restore".
33-35: Good quality translations for multiple paragraphs.These paragraphs have been translated accurately while maintaining the technical meaning of the original text. The translator has done a good job of using appropriate Spanish terminology for technical concepts like "snapshots," "online backup," and "high availability."
Also applies to: 42-44, 51-53, 61-64
postgis-intro/sources/locale/es/LC_MESSAGES/geography_exercises.po (3)
6-6: Metadata updates are consistent with translation project standards.The translator information, revision date, language team URL, and other metadata fields have been properly updated to reflect the current translation effort through the OSGeo Weblate platform.
Also applies to: 12-16, 20-21
26-26: Good translation of the title with appropriate context.The translation "Ejercicios de Datos Tipo Geography" is appropriate since it clarifies that "Geography" refers to the PostGIS data type while providing the Spanish translation for "Exercises" and additional context with "Datos Tipo" (Data Type).
32-33: Note: Many strings remain untranslated.While this update adds the title translation, numerous strings in the file remain untranslated (have empty msgstr entries). This appears to be intentional as part of an incremental translation process.
Also applies to: 36-37, 40-41, 46-47, 52-53, 56-57, 62-63, 68-69, 72-73, 76-77, 80-81, 84-85, 88-89, 92-93, 96-97, 102-103, 108-109, 115-116, 121-122, 129-130
postgis-intro/sources/locale/es/LC_MESSAGES/schemas.po (5)
6-6: Metadata updates look goodThe translation metadata has been properly updated with:
- Current translator information (Paulo Cesar)
- Updated revision date (March 14, 2025)
- Correct language team URL
- Appropriate plural forms configuration
- Generator information (Weblate 5.4.3)
These updates align with modern localization practices and properly credit the translator.
Also applies to: 12-15, 20-21
25-26: Headings translation is accurate and consistentThe section headings have been correctly translated:
- "PostgreSQL Schemas" → "Esquemas en Postgresql"
- "Why use Schemas?" → "¿Por qué usar esquemas?"
- "Creating a Data Schema" → "Creando un Esquema de Datos"
The translations maintain proper Spanish conventions for titles and questions.
Also applies to: 70-71, 133-134
33-36: Introduction and schema concept translations are accurateThe translations accurately convey the technical concepts about PostgreSQL schemas, maintaining proper Spanish technical terminology while preserving the original meaning. The explanation of schemas as folders and the description of PostGIS's use of the public schema are well translated.
Also applies to: 43-46, 54-59, 65-67
74-75: Schema benefits translation is clear and preciseThe translations of the schema benefits section maintain the technical accuracy of the original text while using natural Spanish phrasing. The explanations of bulk actions, data backup advantages, application management, and user isolation are all conveyed clearly in Spanish.
Also applies to: 79-81, 87-90, 97-100, 107-111, 117-119, 126-130
140-257: Note: Remaining sections await translationThe translation work is still in progress, as evidenced by the empty translation strings from line 141 onward. This appears to be part of an ongoing translation effort, with this PR capturing the current progress. These remaining sections cover schema creation, table movement, search paths, and user schemas.
Would you like me to identify which specific sections remain to be translated to help prioritize the next phase of translation work?
postgis-intro/sources/locale/es/LC_MESSAGES/equality.po (1)
6-6: Translation quality looks goodThe Spanish translations accurately convey the meaning of the original English text while using appropriate terminology and natural phrasing. The metadata updates (translator information, revision date, language team URL) follow standard PO file conventions.
Also applies to: 12-15, 20-21, 26-26, 35-39, 43-43, 55-58, 68-73, 86-89, 100-105, 121-124, 126-127, 139-145
postgis-intro/sources/locale/es/LC_MESSAGES/about_data.po (9)
8-8: Updated translator credits with new yearThe translator credits for Paulo Cesar have been updated to include 2025, indicating ongoing contribution to the Spanish translation of the documentation.
14-14: Updated revision date to 2025The PO-Revision-Date has been updated to March 14, 2025, properly tracking the latest revision of this translation file.
112-127: Finalized translation for demographic termsThe fuzzy marker has been removed, indicating that the translation for
popn_blackand its description is now finalized and approved for use. The translation appropriately captures the meaning of people self-identifying as "Black".
120-127: Finalized translation for native population termThe fuzzy marker has been removed, indicating that the translation for
popn_nativand its description is now finalized and approved for use. The translation correctly conveys "Native American" in Spanish.
129-135: Finalized translation for Asian population termThe fuzzy marker has been removed, indicating that the translation for
popn_asianand its description is now finalized and approved for use. The translation appropriately represents "Asian" in Spanish.
137-143: Finalized translation for other population categoriesThe fuzzy marker has been removed, indicating that the translation for
popn_otherand its description is now finalized. The translation correctly captures the concept of "other categories" in Spanish.
145-156: Finalized translation for borough name fieldThe fuzzy marker has been removed, indicating that the translation for
boronameand its description is now finalized. The translation correctly maintains the English borough names while providing the Spanish context.
183-186: Finalized translation for neighborhood termThe fuzzy marker has been removed from the
nyc_neighborhoodstranslation, indicating that it's now approved and finalized.
211-215: Finalized translation for name fieldThe fuzzy marker has been removed from the
namefield translation, indicating that it's now approved for use in the Spanish localization.postgis-intro/sources/locale/es/LC_MESSAGES/simple_sql.po (13)
7-14: Updated translator information and revision dateThe file now credits Paulo Cesar as the translator for 2025 and updates the revision date to March 14, 2025, properly tracking authorship and revision history.
27-27: Improved translation for "Simple SQL"Changed from a direct translation to "SQL Básico," which better conveys the introductory nature of the content in Spanish.
35-37: Enhanced translation for SQL explanationThe translation has been improved to be more natural in Spanish while maintaining the original meaning about SQL being a means to ask questions and update data in relational databases.
44-50: Improved translation for query context and example questionBoth the explanatory text about using SQL for data queries and the example question about neighborhood names have been refined for better clarity and natural phrasing in Spanish.
57-66: Updated UI instruction translationsThe translations for opening the query tool and executing queries have been improved, now correctly referring to the "Herramienta de consulta" button and "Ejecutar consulta" (Play button) in a more natural Spanish phrasing.
79-97: Refined translations for SQL verbs and commandsThe translations for the four main SQL verbs (SELECT, INSERT, UPDATE, DELETE) have been improved with more precise descriptions of their functions in Spanish, better conveying their purpose to Spanish-speaking users.
104-113: Enhanced translation for SELECT functionalityThe explanation of how SELECT is used with spatial functions has been improved for clarity. The heading "SELECT queries" is now appropriately translated as "Consultas SELECT".
121-136: Better translation for query componentsThe explanation of PostgreSQL documentation and query components (columns, data sources, conditions) has been improved with more natural Spanish phrasing while maintaining technical accuracy.
148-156: Improved translation for filter explanationThe explanation of filtering data for Brooklyn neighborhoods has been refined for better clarity and more natural Spanish phrasing.
163-172: Enhanced translation for function applicationThe explanation of applying character length functions to query results has been improved, with a more natural phrasing for the example question about neighborhood name lengths.
190-213: Better translation for aggregate functionsThe explanations of aggregate functions, averages, and standard deviations have been improved with more precise Spanish terminology and natural phrasing.
222-236: Enhanced translation for GROUP BY explanationThe explanation of GROUP BY functionality and its use with aggregate functions has been improved for clarity and natural Spanish phrasing.
259-282: Improved translations for PostgreSQL functionsThe descriptions of PostgreSQL functions (avg, char_length, stddev) have been improved with more natural Spanish phrasing while maintaining technical accuracy.
postgis-intro/sources/locale/es/LC_MESSAGES/geometries.po (2)
12-13: Updated revision date and translator informationThe file now has the updated PO-Revision-Date (March 14, 2025) and credits Paulo Cesar as the Last-Translator, properly tracking authorship and revision history.
300-300: Added translation for ST_Area functionThe previously untranslated ST_Area function now has a proper Spanish translation: ":command:
ST_Area(geometría)devuelve el área de la geometría." This enhances the usability of the documentation for Spanish-speaking users.postgis-intro/sources/locale/es/LC_MESSAGES/joins.po (2)
7-14: Updated translator information and revision dateThe file now credits Paulo Cesar as the translator for 2025 and updates the revision date to March 14, 2025, properly tracking authorship and revision history.
252-254: Added translation for sum() functionThe previously untranslated PostgreSQL aggregate function
sum(expression)now has a proper Spanish translation that explains its purpose is to return the sum of values in a set of records. This completes the documentation of this important aggregate function for Spanish-speaking users.postgis-intro/sources/locale/es/LC_MESSAGES/creating_db.po (3)
7-7: Translator metadata update looks goodMetadata updated to add Paulo Cesar as a translator for 2025, consistent with the PR's purpose of updating translations.
13-14: Updated revision dates and translator informationThe PO-Revision-Date and Last-Translator fields are properly updated to reflect the new translation work.
27-27: Spanish translations are accurate and completeAll translations are technically accurate and correctly reflect the English source text. The translated instructions for PostgreSQL database creation and PostGIS setup are clear and maintain the correct technical terminology.
Also applies to: 31-31, 43-50, 53-53, 61-63, 72-76, 84-86, 90-90, 98-101, 106-107, 112-113, 117-117, 121-121, 125-125, 129-129, 136-137, 144-145, 152-153, 160-161, 166-166, 170-170, 181-183
postgis-intro/sources/locale/es/LC_MESSAGES/3d.po (3)
6-6: Translator metadata update is consistentPaulo Cesar is consistently added as translator across all files, maintaining proper attribution.
8-8: Complete header information in proper formatThe msgstr header contains all required fields formatted correctly according to gettext standards, including updated revision date, translator information, and language settings.
12-12: Comprehensive translation of 3D documentationThe file now contains complete and accurate Spanish translations for the entire 3D chapter, including technical terms like "PointZ", "LinestringZ", and proper formatting of code examples. The translation maintains technical accuracy while providing natural Spanish phrasing.
Also applies to: 16-16, 20-20, 24-24, 28-28, 32-32, 36-36, 40-40, 44-44, 48-48, 52-52, 56-56, 60-60, 64-64, 68-68, 72-72, 76-76, 80-80, 84-84, 88-88, 92-92, 96-96, 100-100, 104-104, 108-108, 112-112, 116-116, 120-120, 124-124, 128-128, 132-132, 136-136, 140-140, 144-144, 148-148, 152-152, 156-156, 160-160, 164-164
postgis-intro/sources/locale/es/LC_MESSAGES/geometry_returning.po (3)
8-8: Translator addition is consistent with other filesPaulo Cesar has been added as translator for 2025, maintaining consistency across all translation files.
14-15: Updated revision metadataThe PO-Revision-Date and Last-Translator fields are properly updated to March 14, 2025.
273-275: New translation for PostgreSQL functionThe translation for the
sum(expression)function is technically accurate and provides clear explanation in Spanish.Note that most of this file remains untranslated (empty msgstr entries), which could be a potential area for future translation work.
postgis-intro/sources/locale/es/LC_MESSAGES/geometry_returning_exercises.po (4)
6-6: Consistent translator informationPaulo Cesar is consistently added as translator for 2025 across all files.
12-16: Updated metadata and language specificationsAll required translation metadata fields are properly updated, including revision date, translator information, and language team details.
20-21: Added plural forms specificationImportant language-specific information has been added for correct pluralization handling in Spanish.
33-34: Translation of exercise hintThe translation of the exercise hint is accurate and naturally worded in Spanish. Note that most of this file remains untranslated (empty msgstr entries), which could be addressed in future translation work.
postgis-intro/sources/locale/es/LC_MESSAGES/projection_exercises.po (3)
6-6: Metadata updates look good.The translator information, revision date, language team URL, and generator information have been correctly updated to the standard format used across the project.
Also applies to: 12-15, 20-21
33-34: Good translation of the hint text.The Spanish translation accurately conveys the meaning of the original hint text about functions being useful for exercises.
62-63: Accurate translation of ST_AsText function description.The translation correctly explains that the function returns the geometry representation in WKT format.
postgis-intro/sources/locale/es/LC_MESSAGES/spatial_relationships_exercises.po (1)
6-6: Metadata updates look good.The translator information, revision date, language team URL, and generator information have been correctly updated to match the project's standard format.
Also applies to: 12-15, 20-21
postgis-intro/sources/locale/es/LC_MESSAGES/joins_advanced.po (3)
6-6: Metadata updates look good.The translator information, revision date, language team URL, and generator information have been correctly updated to match the project's standard format.
Also applies to: 12-15, 20-21
26-26: Good translation of section title."More Spatial Joins" has been accurately translated to "Más Joins Espaciales", maintaining technical terminology.
34-36: Good translation of function descriptions.The paragraph explaining the ST_Centroid and ST_Union functions has been accurately translated while preserving the command formatting.
postgis-intro/sources/locale/es/LC_MESSAGES/geometries_exercises.po (3)
12-13: Metadata updates look good.The metadata has been correctly updated with the new translator information, revision date, and language team URL.
Also applies to: 14-15, 20-21
89-89: Good translation of ST_Area function.The translation accurately describes the function's purpose while preserving the command formatting.
131-132: Good translation of ST_AsText function.The translation correctly explains that the function returns the geometry representation in WKT format.
postgis-intro/sources/locale/es/LC_MESSAGES/joins_exercises.po (2)
66-67: Maintain function names consistency in translation.The function name
ST_Containshas been translated toST_Contiene. For consistency with PostGIS documentation, consider keeping original function names untranslated while translating only the parameters and descriptions.
74-75: Maintain function names consistency in translation.The function name
ST_Distancehas been translated toST_Distancia. PostGIS function names should remain in their original form to maintain consistency with the official documentation and avoid confusion for users.postgis-intro/sources/locale/es/LC_MESSAGES/simple_sql_exercises.po (1)
159-172: Great job on the function descriptions.The translations for the SQL aggregation functions are accurate and maintain the technical meaning while being clear in Spanish. This will help Spanish-speaking users understand these important database concepts.
|
|
||
| #: ../../en/joins_exercises.rst:10 | ||
| msgid ":command:`ST_Area(geometry)` returns the area of the polygons" | ||
| msgstr "" | ||
| msgstr ":command:`ST_Area(geometría)` devuelve el área de la geometría." |
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
Maintain function names consistency in translation.
The function name ST_Area has been translated in the Spanish version, but PostGIS function names should typically remain unchanged while only translating parameters and descriptions. Consider keeping the original function name to avoid confusion for users referencing the PostGIS documentation.
🏁 Script executed:
#!/bin/bash
# Check for other translations that might have kept function names unchanged
grep -E "ST_[A-Za-z]+" --include="*.po" -r postgis-intro/sources/locale/es/LC_MESSAGES/ | grep -v "ST_Area\|ST_Contiene\|ST_Distancia"Length of output: 68345
Action Required: Fix function name translation for consistency with PostGIS docs.
-
In the file
postgis-intro/sources/locale/es/LC_MESSAGES/joins_exercises.po(line 53), the message currently reads:msgstr ":command:`ST_Area(geometría)` devuelve el área de la geometría." -
To conform to the convention seen in other translations (where PostGIS function names remain in English), please update the message so that it preserves the original function name. For example, change it to:
msgstr ":command:`ST_Area(geometry)` devuelve el área de la geometría."
This adjustment ensures consistency with the official PostGIS documentation and avoids potential confusion.
osgeoweblate
force-pushed
the
weblate-postgis-workshop-index
branch
from
fa082ce to
03f5e95
Compare
There was a problem hiding this comment.
Actionable comments posted: 0
♻️ Duplicate comments (1)
postgis-intro/sources/locale/es/LC_MESSAGES/equality.po (1)
125-125:⚠️ Potential issueFix incorrect translation of Sphinx markup
The Sphinx documentation markup
:command:has been incorrectly translated to:comando:. This should remain as:command:since it's part of the documentation system syntax, not translatable content.-proporciona el operador de límites iguales, :comando:`~=`. Este operador +proporciona el operador de límites iguales, :command:`~=`. Este operador
🧹 Nitpick comments (1)
postgis-intro/sources/locale/es/LC_MESSAGES/schemas.po (1)
136-257: Translation needed for practical schema usage sections.The conceptual parts of the document have been translated, but the practical sections about creating schemas, moving tables, setting search paths, and creating user schemas remain untranslated. Consider prioritizing these sections in future translation work as they contain important hands-on information.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (20)
postgis-intro/sources/locale/es/LC_MESSAGES/3d.po(1 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/about_data.po(1 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/advanced_geometry_construction.po(1 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/backup.po(1 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/creating_db.po(5 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/equality.po(7 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/geography_exercises.po(1 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/geometries.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/geometries_exercises.po(3 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/geometry_returning.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/geometry_returning_exercises.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/joins.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/joins_advanced.po(1 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/joins_exercises.po(1 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/license.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/projection_exercises.po(3 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/schemas.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/simple_sql.po(7 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/simple_sql_exercises.po(8 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/spatial_relationships_exercises.po(2 hunks)
🚧 Files skipped from review as they are similar to previous changes (16)
- postgis-intro/sources/locale/es/LC_MESSAGES/simple_sql.po
- postgis-intro/sources/locale/es/LC_MESSAGES/about_data.po
- postgis-intro/sources/locale/es/LC_MESSAGES/geometries.po
- postgis-intro/sources/locale/es/LC_MESSAGES/license.po
- postgis-intro/sources/locale/es/LC_MESSAGES/creating_db.po
- postgis-intro/sources/locale/es/LC_MESSAGES/projection_exercises.po
- postgis-intro/sources/locale/es/LC_MESSAGES/geometry_returning.po
- postgis-intro/sources/locale/es/LC_MESSAGES/spatial_relationships_exercises.po
- postgis-intro/sources/locale/es/LC_MESSAGES/geometry_returning_exercises.po
- postgis-intro/sources/locale/es/LC_MESSAGES/backup.po
- postgis-intro/sources/locale/es/LC_MESSAGES/joins.po
- postgis-intro/sources/locale/es/LC_MESSAGES/geometries_exercises.po
- postgis-intro/sources/locale/es/LC_MESSAGES/joins_advanced.po
- postgis-intro/sources/locale/es/LC_MESSAGES/geography_exercises.po
- postgis-intro/sources/locale/es/LC_MESSAGES/joins_exercises.po
- postgis-intro/sources/locale/es/LC_MESSAGES/simple_sql_exercises.po
🔇 Additional comments (8)
postgis-intro/sources/locale/es/LC_MESSAGES/advanced_geometry_construction.po (4)
7-7: LGTM! Appropriate translator credit added.The addition of Paulo Cesar as a translator for 2025 is consistent with the metadata updates across the PR.
13-14: LGTM! Metadata properly updated.The revision date, translator information, and Weblate generator version have been appropriately updated to reflect the new translation work.
Also applies to: 22-22
27-27: Translation added for the key section heading.Good addition of the Spanish translation for "Advanced Geometry Constructions" as "Construcción de Geometrías". Note that the English uses plural "Constructions" while the Spanish uses singular "Construcción" - this appears to be a deliberate stylistic choice for better readability in Spanish.
351-351: LGTM! Existing translation retained.The translation for "See Also" as "Ver también" has been properly retained from the previous version.
postgis-intro/sources/locale/es/LC_MESSAGES/3d.po (2)
6-8: Metadata properly updated with translator information.The translator information has been correctly added, including name, email, and revision date. This is consistent with best practices for translation files.
12-164: Complete and accurate Spanish translations for 3D PostGIS concepts.The translations are technically accurate and maintain the precise meaning of the original English content. Technical terms are properly preserved (e.g., "POINT ZM", "POLYHEDRALSURFACE") while explanatory text has been well-translated into natural Spanish. All sections have been translated, providing a complete Spanish version of the 3D PostGIS documentation.
postgis-intro/sources/locale/es/LC_MESSAGES/schemas.po (2)
6-22: Metadata properly updated with translator information.The translator information has been correctly added, including name, email, and revision date. The plural forms and generator information have also been properly set.
26-134: Partial translation completed for PostgreSQL schemas concepts.The conceptual sections explaining what schemas are and their benefits have been well translated into Spanish. However, the practical sections about creating and using schemas (lines 136-257) remain untranslated. This is normal in an ongoing translation project.
Would you like me to check the translation progress for this file or other files in the project?
osgeoweblate
force-pushed
the
weblate-postgis-workshop-index
branch
2 times, most recently
from
3491d19 to
6119db2
Compare
There was a problem hiding this comment.
Actionable comments posted: 0
🔭 Outside diff range comments (1)
postgis-intro/sources/locale/es/LC_MESSAGES/advanced_geometry_construction.po (1)
314-427: 💡 Verification agent🧩 Analysis chain
Missing translations for significant portions of technical content.
There are several untranslated sections from line 314 onwards, covering important technical explanations about PostgreSQL arrays, recursive CTEs, and the process of building route lines.
Please consider completing the translations for these sections to ensure consistent documentation quality for Spanish-speaking users. These sections contain valuable technical information about PostgreSQL and PostGIS functionality.
🌐 Web query:
Are there any PostgreSQL or PostGIS Spanish translation glossaries available?💡 Result:
PostgreSQL and PostGIS have several resources and community-driven efforts for Spanish translations that effectively serve as glossaries, though explicit standalone glossaries aren't directly listed. Here's a breakdown:
PostgreSQL Resources
Official Documentation:
The PostgreSQL community maintains localized resources, including Spanish translations of error messages and documentation. The PostgreSQL wiki outlines structured processes for translating releases and coordinating language-specific efforts (e.g., Spanish teams using Git for collaboration) [4]. While not a formal glossary, these efforts standardize terminology.Localization Tools:
PostgreSQL supports locale configurations (e.g.,LC_COLLATE,LC_CTYPE) for Spanish sorting, formatting, and translated system messages [7][12]. Built-in text search dictionaries likespanish_stemalso handle Spanish-language tokenization [6][12].PostGIS Resources
Spanish Manual:
The PostGIS documentation is partially translated into Spanish, covering core concepts like spatial data types and functions [2][5][11]. This serves as a de facto glossary by embedding standardized terminology.Collaborative Translation Platforms:
The PostGIS workshop materials are actively translated via OSGeo Weblate, involving community contributors to ensure consistency [20]. This platform likely uses shared terminology databases.Books and Training:
- PostGIS: Análisis Espacial Avanzado (2nd ed.) by José Carlos Martínez Llario is a comprehensive Spanish-language resource [14].
- The Introduction to PostGIS workshop includes Spanish-language data and exercises [14].
Community Efforts
- Translation Workflows: Tools like the Localazy CLI demonstrate methods for extracting and translating database content into Spanish, suggesting implicit glossary use during JSON-based workflows [3].
- PostGIS In Action Translations: Interest exists for Spanish editions of books like PostGIS In Action, which would include curated terminology [17].
While no standalone Spanish glossary is explicitly mentioned, these resources collectively provide standardized terminology. For specific terms, the PostGIS Spanish manual and PostgreSQL localization guidelines are primary references [2][4][5].
Citations:
- 1: https://www.youtube.com/watch?v=Gtz883daf1Y
- 2: https://postgis.net/docs/manual-dev/postgis-es.html
- 3: https://localazy.com/blog/how-to-translate-content-in-postgresql-database-with-localazy
- 4: https://wiki.postgresql.org/wiki/HowToTranslate
- 5: https://postgis.net/docs/manual-dev/es/
- 6: https://www.postgresql.org/docs/current/textsearch-dictionaries.html
- 7: https://www.postgresql.org/docs/7.2/charset.html
- 8: https://postgis.net/documentation/manual/
- 9: https://docs.digitalocean.com/products/databases/postgresql/details/supported-extensions/
- 10: https://www.postgresql.org/docs/current/glossary.html
- 11: https://geo.cepal.org/en/contenido/categoria-ide/tecnolog%C3%ADa/archivos/pdf/postgis-manual.pdf
- 12: https://devcenter.heroku.com/articles/heroku-postgres-extensions-postgis-full-text-search
- 13: https://www.postgresql.org/message-id/[email protected]
- 14: https://postgis.net/documentation/training/
- 15: https://wiki.postgresql.org/wiki/FAQ
- 16: https://postgrespro.com/list/thread-id/1469052
- 17: https://www.postgis.us/page_translations
- 18: https://aws.amazon.com/about-aws/whats-new/2021/10/amazon-aurora-postgresql-supports-postgis/
- 19: https://context.reverso.net/translation/english-spanish/postgresql
- 20: https://weblate.osgeo.org/projects/postgis-workshop/loading_data/es/
Action Required: Complete Untranslated Technical Sections
The file postgis-intro/sources/locale/es/LC_MESSAGES/advanced_geometry_construction.po (lines 314–427) still contains extensive untranslated content—covering technical details such as PostgreSQL array functions, recursive CTEs, and the process of constructing route lines. This technical material is crucial for Spanish-speaking users to fully understand PostgreSQL and PostGIS functionalities.
Please ensure all these sections are accurately translated. For consistency, consider referring to available community resources like the PostGIS Spanish Manual and the PostgreSQL translation guidelines.
♻️ Duplicate comments (2)
postgis-intro/sources/locale/es/LC_MESSAGES/equality.po (1)
125-125:⚠️ Potential issueFix incorrect translation of Sphinx markup
The Sphinx documentation markup
:command:has been incorrectly translated to:comando:. This should remain as:command:since it's part of the documentation system syntax, not translatable content.-"proporciona el operador de límites iguales, :comando:`~=`. Este operador " +"proporciona el operador de límites iguales, :command:`~=`. Este operador "postgis-intro/sources/locale/es/LC_MESSAGES/simple_sql_exercises.po (1)
212-212:⚠️ Potential issueFix mistranslation that changes the exercise meaning.
The original question asks about the percentage of white population ("what percentage of the population is white?"), but the Spanish translation asks about black population ("¿Qué porcentaje de población negra hay en cada distrito?"). This changes the meaning of the exercise.
-msgstr "**¿Qué porcentaje de población negra hay en cada distrito?" +msgstr "**¿Qué porcentaje de población blanca hay en cada distrito?"
🧹 Nitpick comments (2)
postgis-intro/sources/locale/es/LC_MESSAGES/simple_sql_exercises.po (1)
184-184: Fix missing closing quotation mark.The Spanish translation is missing a closing quotation mark at the end of the question.
-**¿Cuántas calles de Nueva York empiezan por \"B\"?" +**¿Cuántas calles de Nueva York empiezan por \"B\"?**"postgis-intro/sources/locale/es/LC_MESSAGES/advanced_geometry_construction.po (1)
429-453: Missing translations for "See Also" section links.The "See Also" section header is translated, but the links to PostgreSQL and PostGIS documentation remain untranslated. Consider translating the descriptive text for these links while keeping the URLs unchanged.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (21)
postgis-intro/sources/locale/es/LC_MESSAGES/3d.po(1 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/about_data.po(1 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/advanced_geometry_construction.po(7 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/backup.po(1 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/creating_db.po(5 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/equality.po(7 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/geography.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/geography_exercises.po(1 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/geometries.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/geometries_exercises.po(3 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/geometry_returning.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/geometry_returning_exercises.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/joins.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/joins_advanced.po(1 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/joins_exercises.po(1 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/license.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/projection_exercises.po(3 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/schemas.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/simple_sql.po(7 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/simple_sql_exercises.po(8 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/spatial_relationships_exercises.po(2 hunks)
🚧 Files skipped from review as they are similar to previous changes (17)
- postgis-intro/sources/locale/es/LC_MESSAGES/simple_sql.po
- postgis-intro/sources/locale/es/LC_MESSAGES/geography.po
- postgis-intro/sources/locale/es/LC_MESSAGES/geometry_returning.po
- postgis-intro/sources/locale/es/LC_MESSAGES/3d.po
- postgis-intro/sources/locale/es/LC_MESSAGES/about_data.po
- postgis-intro/sources/locale/es/LC_MESSAGES/geometry_returning_exercises.po
- postgis-intro/sources/locale/es/LC_MESSAGES/geometries.po
- postgis-intro/sources/locale/es/LC_MESSAGES/spatial_relationships_exercises.po
- postgis-intro/sources/locale/es/LC_MESSAGES/geography_exercises.po
- postgis-intro/sources/locale/es/LC_MESSAGES/projection_exercises.po
- postgis-intro/sources/locale/es/LC_MESSAGES/schemas.po
- postgis-intro/sources/locale/es/LC_MESSAGES/joins_advanced.po
- postgis-intro/sources/locale/es/LC_MESSAGES/geometries_exercises.po
- postgis-intro/sources/locale/es/LC_MESSAGES/joins.po
- postgis-intro/sources/locale/es/LC_MESSAGES/creating_db.po
- postgis-intro/sources/locale/es/LC_MESSAGES/license.po
- postgis-intro/sources/locale/es/LC_MESSAGES/joins_exercises.po
🔇 Additional comments (15)
postgis-intro/sources/locale/es/LC_MESSAGES/backup.po (9)
6-6: Updated translator information is correctly formatted.The translator information has been properly updated with the name "Paulo Cesar" and email "[email protected]" along with the year 2025.
12-16: Correctly updated PO file metadata.The translation metadata has been properly updated with:
- Current revision date (2025-03-14)
- Consistent translator information
- Appropriate language team URL
- Language identifier (es)
This follows standard gettext PO file conventions.
20-21: Added required plural forms rule and generator information.The additions are correct:
- The plural forms rule (
nplurals=2; plural=n != 1) matches Spanish language requirements- The X-Generator field properly identifies Weblate as the translation tool
26-26: Accurate translation of the document title.The translation "Copia de seguridad y restauración de PostgreSQL" correctly conveys the meaning of "PostgreSQL Backup and Restore" in Spanish.
33-35: Well-translated introduction paragraph.The translation accurately conveys the original meaning about different backup methods for PostgreSQL databases, with natural-sounding Spanish phrasing.
42-44: Good translation with helpful clarification.The translation correctly includes the English term "snapshots" in parentheses after "instantáneas" to help Spanish readers understand the technical term. This is good practice for technical documentation.
51-53: Accurate translation of online backup concept.The Spanish translation correctly preserves the meaning of online backup schemes while maintaining natural language flow.
61-64: Correctly translated paragraph with preserved hyperlink.The translation accurately conveys the information about high availability while correctly maintaining the hyperlink formatting from the original text.
7-484:❓ Verification inconclusive
Note about untranslated content.
This appears to be an incremental translation update. Many sections remain untranslated (empty msgstr entries), which is normal for ongoing translation projects. The translated content is of good quality, and the remaining untranslated sections can be addressed in future updates.
🏁 Script executed:
#!/bin/bash # Count total and translated messages in the file echo "Translation statistics for backup.po:" msgfmt --statistics postgis-intro/sources/locale/es/LC_MESSAGES/backup.poLength of output: 257
Translation File Update – Please Manually Verify Translation Statistics
The translation file atpostgis-intro/sources/locale/es/LC_MESSAGES/backup.pois being updated incrementally. As noted, manymsgstrentries remain empty, which is expected for an ongoing translation project. Although the original verification usingmsgfmtfailed (due to the tool not being available in the current environment), this does not affect the translation quality per se.To further verify the translation statistics manually, please run the following alternative shell script which uses
grepto count total and non-empty entries:#!/bin/bash echo "Counting msgid entries:" total_msgids=$(grep -c '^msgid ' postgis-intro/sources/locale/es/LC_MESSAGES/backup.po) echo "Total msgid entries: $total_msgids" echo "Counting non-empty msgstr entries:" non_empty_msgstr=$(grep -c '^msgstr "[^"]' postgis-intro/sources/locale/es/LC_MESSAGES/backup.po) echo "Non-empty msgstr entries: $non_empty_msgstr"Key Points:
- The file shows expected incremental updates with several untranslated sections (empty
msgstrentries).- The translated content that is present is of good quality.
- Future updates can continue to fill in the remaining translations.
Please review the output of the above script to confirm the translation completeness and ensure everything is in order.
postgis-intro/sources/locale/es/LC_MESSAGES/advanced_geometry_construction.po (6)
6-7: Metadata updates look good.The translator information, revision date, and Weblate version have been properly updated to reflect the current translation effort.
Also applies to: 13-14, 22-22
26-27: Good translation of the document title."Construcción de Geometrías" is an appropriate translation for "Advanced Geometry Constructions".
33-47: Well-translated technical content.The translation effectively preserves technical terms like "nyc_subway_stations" while maintaining natural Spanish phrasing to explain the purpose of the chapter.
59-74: Good handling of technical concepts.The translation appropriately explains the two issues with the subway stations data while maintaining technical accuracy and Spanish language fluency.
183-205: Excellent technical translation.The explanation of PostgreSQL arrays and the array operators is well-translated, preserving the technical accuracy while making it understandable in Spanish.
215-220: Good translation of PostGIS-specific content.The translation correctly maintains the PostGIS function name
ST_MakeLinewhile translating the surrounding explanatory text appropriately.
osgeoweblate
force-pushed
the
weblate-postgis-workshop-index
branch
from
6119db2 to
410125f
Compare
There was a problem hiding this comment.
Actionable comments posted: 0
🔭 Outside diff range comments (2)
postgis-intro/sources/locale/es/LC_MESSAGES/advanced_geometry_construction.po (2)
314-410:⚠️ Potential issueMissing translations for several sections.
Multiple sections from line 314 to line 410 have not been translated yet. This includes important explanations about finding distinct routes, working with PostgreSQL array functions, building route lines, and the visualization results.
These sections contain crucial information about:
- Working out what routes exist
- Using PostgreSQL array functions
- Creating tables for each route's stations
- Finding center points of routes
- Generating route lines
- Visualizing the results in QGIS
Please complete these translations to ensure Spanish readers have access to the complete documentation.
437-453:⚠️ Potential issueMissing translations for reference links.
The "See Also" section contains several important reference links that have not been translated yet. While the URLs would remain the same, the descriptive text should be translated to help Spanish readers understand what each link references.
Please translate the text descriptions for these links to PostgreSQL documentation on Arrays, Array Functions, Recursive Common Table Expressions, and PostGIS ST_MakeLine.
🧹 Nitpick comments (5)
postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/history_tracking.po (1)
59-65: Consider completing the remaining translationsThere are still many strings in this file that remain untranslated. Consider prioritizing the completion of these translations in a future update to provide a comprehensive Chinese localization of the history tracking documentation.
Also applies to: 69-105, 109-147, 151-198, 202-216, 220-244, 248-250, 258-270
postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/3d.po (1)
31-40: Many strings still require translationA significant portion of the content remains untranslated. Consider completing these translations in a future update to provide a comprehensive documentation experience for Chinese readers.
Also applies to: 42-43, 62-163
postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/equality.po (1)
49-73: Several key sections remain untranslatedMultiple important sections explaining spatial equality and equal bounds concepts are still untranslated. Consider completing these translations in a future update to provide comprehensive documentation for Chinese users.
postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/clusterindex.po (1)
65-160: Note: Several sections remain untranslated.While this PR adds several valuable translations, many sections of the document remain untranslated, including "Clustering on the R-Tree," "Disk Versus Memory/SSD," and other important technical sections. Consider translating these sections in a future update.
Would you like me to help identify which sections should be prioritized for the next translation batch?
postgis-intro/sources/locale/es/LC_MESSAGES/advanced_geometry_construction.po (1)
27-27: Good translation but slightly abbreviated.The translation "Construcción de Geometrías" is accurate but slightly abbreviated compared to the original "Advanced Geometry Constructions" (missing the "Advanced" qualifier). Consider using "Construcción Avanzada de Geometrías" to fully capture the original meaning.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (30)
postgis-intro/sources/locale/es/LC_MESSAGES/3d.po(1 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/about_data.po(1 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/advanced_geometry_construction.po(7 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/backup.po(1 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/creating_db.po(5 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/equality.po(7 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/geography.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/geography_exercises.po(1 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/geometries.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/geometries_exercises.po(3 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/geometry_returning.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/geometry_returning_exercises.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/joins.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/joins_advanced.po(1 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/joins_exercises.po(1 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/license.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/projection_exercises.po(3 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/schemas.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/simple_sql.po(7 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/simple_sql_exercises.po(8 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/spatial_relationships_exercises.po(2 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/3d.po(2 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/advanced_geometry_construction.po(1 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/clusterindex.po(2 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/equality.po(1 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/history_tracking.po(2 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/index.po(2 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/license.po(2 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/spatial_relationships.po(2 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/upgrades.po(3 hunks)
🚧 Files skipped from review as they are similar to previous changes (19)
- postgis-intro/sources/locale/es/LC_MESSAGES/simple_sql.po
- postgis-intro/sources/locale/es/LC_MESSAGES/geography.po
- postgis-intro/sources/locale/es/LC_MESSAGES/joins.po
- postgis-intro/sources/locale/es/LC_MESSAGES/license.po
- postgis-intro/sources/locale/es/LC_MESSAGES/about_data.po
- postgis-intro/sources/locale/es/LC_MESSAGES/geography_exercises.po
- postgis-intro/sources/locale/es/LC_MESSAGES/geometry_returning.po
- postgis-intro/sources/locale/es/LC_MESSAGES/schemas.po
- postgis-intro/sources/locale/es/LC_MESSAGES/spatial_relationships_exercises.po
- postgis-intro/sources/locale/es/LC_MESSAGES/joins_advanced.po
- postgis-intro/sources/locale/es/LC_MESSAGES/backup.po
- postgis-intro/sources/locale/es/LC_MESSAGES/creating_db.po
- postgis-intro/sources/locale/es/LC_MESSAGES/equality.po
- postgis-intro/sources/locale/es/LC_MESSAGES/geometries.po
- postgis-intro/sources/locale/es/LC_MESSAGES/geometries_exercises.po
- postgis-intro/sources/locale/es/LC_MESSAGES/projection_exercises.po
- postgis-intro/sources/locale/es/LC_MESSAGES/geometry_returning_exercises.po
- postgis-intro/sources/locale/es/LC_MESSAGES/joins_exercises.po
- postgis-intro/sources/locale/es/LC_MESSAGES/simple_sql_exercises.po
🔇 Additional comments (69)
postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/spatial_relationships.po (3)
11-11: Metadata update looks good.The PO-Revision-Date has been updated to reflect the most recent translation update (March 25, 2025). This is standard practice for localization files to track when translations were last revised.
29-31: Accurate translation of spatial functions explanation.The translation correctly conveys that the spatial functions discussed so far only work on one geometry at a time, including the measurement functions (ST_Area, ST_Length), serialization (ST_GeomFromText), and deserialization (ST_AsGML) functions. The technical terminology is maintained appropriately.
35-36: Proper translation of spatial database capabilities.The translation accurately explains that the power of spatial databases comes not just from storing geometric data but also from their ability to analyze relationships between geometries. The emphasis on "几何体之间的空间关系" correctly preserves the original formatting and emphasis.
postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/history_tracking.po (3)
6-6: Update to translator information looks goodThe addition of Wangdapeng as a new translator for 2025 is properly formatted and consistent with the localization update pattern seen across files in this PR.
12-13: Metadata updates are consistently appliedThe revision date, translator information, and generator version have been appropriately updated to reflect the current translation effort. The consistency of these metadata fields across files is commendable.
Also applies to: 21-21
25-25: Good quality translations with appropriate formattingThe newly added Chinese translations accurately convey the meaning of the original English text while maintaining readability in Chinese. The translations effectively explain the concepts of history tracking in database systems.
Also applies to: 35-37, 44-45, 51-51, 55-55
postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/3d.po (3)
5-5: Translator information consistently updatedThe addition of Wangdapeng as a translator for 2025 maintains consistency with other files in this PR.
7-7: Metadata block properly formattedThe consolidated metadata block contains all necessary information and follows the expected format for PO files. The inclusion of the language team URL and other metadata is appropriate.
19-19: Clear and accurate translations for 3D conceptsThe translations effectively convey the technical concepts related to 3D geometries in PostGIS, maintaining accuracy while ensuring readability in Chinese.
Also applies to: 23-23, 27-27
postgis-intro/sources/locale/es/LC_MESSAGES/3d.po (3)
6-6: Translator information appropriately updatedThe addition of Paulo Cesar as a translator for 2025 is correctly formatted and consistent with the localization update pattern for Spanish files.
8-8: Well-formatted metadata with complete informationThe consolidated metadata block includes all necessary information following the standard PO file format, with proper specification of language team, plural forms, and generator version.
12-164: Comprehensive and high-quality Spanish translationsThe Spanish translations are exceptionally thorough, covering the entire document with accurate technical translations. The terminology is consistent and appropriate for a technical audience while maintaining natural Spanish language flow. This provides an excellent example of complete localization.
postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/equality.po (3)
5-5: Consistent translator informationThe addition of Wangdapeng as a translator maintains consistency with other Chinese localization files in this PR.
11-14: Properly updated metadata fieldsThe revision date, translator information, language team details, and plural forms are all correctly specified according to PO file standards.
Also applies to: 19-20
25-25: Clear translations of equality conceptsThe translations accurately convey the technical concepts related to geometric equality in PostGIS, with particular attention to precise terminology in Chinese.
Also applies to: 30-32, 36-36, 40-40, 44-45
postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/upgrades.po (4)
5-5: Author information updated correctly.The translator information has been updated to include Wangdapeng as a new contributor for 2025.
11-14: Metadata updates look good.The PO-Revision-Date, Last-Translator, and Language-Team fields have been properly updated with the new translator's information and current date.
19-20: Formatting metadata properly updated.The plural forms specification and generator version have been correctly updated to the latest standards.
24-24: Translations added successfully.New translations have been properly added for previously untranslated strings, improving documentation accessibility for Chinese users. The translations accurately convey the meaning of the original English text.
Also applies to: 33-35, 45-47, 51-51, 55-55
postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/advanced_geometry_construction.po (4)
4-4: Author information updated correctly.The translator information has been updated to include Wangdapeng with years 2024 and 2025.
10-13: Metadata updates look good.The PO-Revision-Date, Last-Translator, and Language-Team fields have been properly updated with the new translator's information and current date.
18-19: Formatting metadata properly updated.The plural forms specification and generator version have been correctly updated to the latest standards.
23-23: Translations added successfully.New translations have been properly added for previously untranslated sections, improving the documentation for Chinese users. The translations accurately reflect the technical content of the original English text.
Also applies to: 27-28, 33-34, 38-38
postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/index.po (3)
5-5: Author information updated correctly.The new translator Wangdapeng has been properly credited for 2025 contributions.
7-7: Metadata updated in consolidated format.All metadata fields (PO-Revision-Date, Last-Translator, Language-Team, etc.) have been updated in a single line, which is valid for PO files.
19-19: Translation refinement improves clarity.The translation for the data bundle message has been refined to be more concise while maintaining the original meaning, which improves readability for Chinese users.
postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/license.po (4)
5-5: Author information updated correctly.The translator information has been updated to include Wangdapeng as a contributor for 2025.
11-14: Metadata updates look good.The PO-Revision-Date, Last-Translator, and Language-Team fields have been properly updated with the new translator's information and current date.
19-20: Formatting metadata properly updated.The plural forms specification and generator version have been correctly updated to the latest standards.
24-24: License translations properly completed.The previously untranslated license information has been accurately translated into Chinese, which is important for ensuring users understand the licensing terms of the documentation.
Also applies to: 33-36, 42-42
postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/clusterindex.po (6)
5-5: Metadata updates look good.The metadata has been properly updated with the new translator information (Wangdapeng), revision date (March 25, 2025), and Weblate generator version (5.4.3).
Also applies to: 11-12, 20-20
24-24: Translation for "Clustering on Indices" added correctly.The Chinese translation "索引聚类" has been appropriately added for the section title.
33-35: Good translation of the database performance paragraph.This translation accurately conveys the technical concept of how database size affects disk access limitations, with appropriate technical terminology.
42-43: Appropriate translation of data storage concepts.The translation correctly captures the concept that data storage order on disk is opportunistic and may not correlate with access patterns.
50-51: Clear translation of clustering concept.The translation effectively explains the concept of clustering and its benefits for data access speed, with the term "聚类" (clustering) appropriately highlighted.
58-59: Good translation of clustering scheme principles.The translation accurately conveys the relationship between index ordering and data access patterns.
postgis-intro/sources/locale/es/LC_MESSAGES/advanced_geometry_construction.po (33)
7-7: Metadata updates look appropriate.The file has been updated with new translator information (Paulo Cesar), a more recent revision date (March 18, 2025), and the latest Weblate generator version (5.4.3). These metadata changes are standard for translation updates and correctly follow PO file formatting conventions.
Also applies to: 13-14, 22-22
34-35: Excellent translation with proper formatting.The translation accurately conveys the meaning of the original text while maintaining the backtick formatting for the code element
nyc_subway_stations.
44-47: Well-structured translation with preserved technical elements.This translation effectively conveys the meaning while maintaining the natural flow in Spanish. The technical terms "PostgreSQL" and "PostGIS" are correctly preserved, and the backticks for code formatting are properly maintained.
51-51: Good translation with elegant restructuring.The translation "Dos cuestiones dificultan nuestra tarea:" elegantly restructures the original "Our task is made especially difficult by two issues:" to sound more natural in Spanish while preserving the meaning.
59-61: Accurate translation with proper code element formatting.The translation correctly preserves the technical elements with backticks and accurately conveys the meaning of the original text about how the
routescolumn contains multiple route identifiers.
70-74: Well-constructed translation that maintains technical accuracy.This longer passage has been translated with attention to detail, preserving the technical meaning regarding route ordering information while maintaining natural Spanish phrasing.
81-82: Good translation with proper question formatting in Spanish.The translation correctly uses the Spanish opening question mark (¿) at the beginning of the question, which is a proper Spanish punctuation practice that differs from English.
86-86: Appropriate translation with proper quotation marks.The translation correctly uses quotation marks around "Q" and properly translates "stops" as "paradas", which is the appropriate term for subway stops in Spanish.
93-93: Good translation with preserved code formatting.The translation accurately conveys the meaning while maintaining the backtick formatting for the code element
gid.
101-104: Well-structured translation with technical accuracy.This translation effectively conveys the meaning of the original text about starting at end stations and finding the next closest station, while maintaining natural Spanish sentence structure.
109-110: Good translation with proper terminology.The translation correctly captures the meaning of "iterative routine" as "rutina iterativa", maintaining the technical accuracy of the original text.
117-118: Good translation with preserved links and proper terminology.Both translations for the procedural language options maintain the original links and correctly translate the technical concepts. The translation of "common table expressions" as "expresiones comunes" is accurate.
Also applies to: 125-126
134-137: Excellent translation with preserved technical elements.This translation accurately conveys the concept of Common Table Expressions (CTEs) while maintaining proper backtick formatting for code elements and preserving the variable name
gid.
141-141: Simple but accurate translation.The translation is concise and accurately conveys the meaning of the original text about the CTE consisting of two halves.
149-151: Good translation with technical accuracy.The translation accurately conveys the explanation of the first half of the CTE, maintaining the technical meaning and proper formatting for the quoted "gid" term.
162-167: Excellent technical translation with preserved code elements.This translation effectively conveys the complex technical explanation about iterating through stops and using array operations while maintaining proper formatting for all code elements with double asterisks.
174-175: Good translation of technical description.The translation accurately conveys the message about advanced PostgreSQL features being used beyond the recursive CTE.
183-185: Well-structured translation with preserved technical meaning.This translation effectively maintains the enthusiasm of the original text with "¡Estamos usando ARRAY!" and accurately explains the array functionality in PostgreSQL.
191-192: Good translation with preserved function name.The translation correctly maintains the function name array_append with its formatting while accurately translating the purpose of building an array of visited identifiers.
201-205: Excellent technical translation.This complex explanation about the array contains operator is accurately translated with maintained technical terminology and proper formatting for code elements.
215-220: Well-structured translation with preserved links and technical accuracy.This translation maintains the technical explanation about the ST_MakeLine function while preserving the link formatting and accurately conveying the concept of converting geometries into a single linear output.
224-224: Concise translation that works well.The translation "La cual luce como:" is a good way to express "Which looks like this:" in Spanish, maintaining the flow of the document.
228-228: Simple but effective translation.The translation "Éxito!" correctly includes the asterisks for formatting and properly translates "Success!" while maintaining the exclamation mark.
232-232: Good translation with proper Spanish syntax.The translation "Excepto por dos problemas:" effectively conveys the meaning while adapting to natural Spanish structure.
239-240: Accurate translation that maintains technical meaning.This translation correctly conveys the point about calculating all routes rather than just one.
248-250: Well-structured translation with preserved technical term.The translation accurately conveys the concept of "a priori knowledge" while maintaining the italics formatting and explaining the purpose of the initial station identifier.
257-259: Good translation with natural Spanish flow.This translation effectively maintains the meaning about identifying the first station without manually examining the set, adapting the phrasing to sound natural in Spanish.
266-267: Good translation with proper quotation marks.The translation correctly uses quotation marks around "Q" and properly translates the question about what characterizes end stations.
275-277: Excellent translation with added clarification.The translation not only conveys the meaning but improves clarity by adding parenthetical explanations for "septentrionales" and "meridionales" after "norte" and "sur," helping Spanish readers understand these more formal geographical terms.
286-289: Well-structured translation that maintains technical meaning.This translation effectively conveys the concept of characterizing end stations by their distance from the middle rather than by cardinal directions.
296-297: Good translation with proper Spanish phrasing.The translation correctly conveys the idea of testing the second rule since there is no perfect heuristic for identifying end points.
305-307: Excellent translation with proper localization.This translation effectively conveys the explanation about the failure mode of the "furthest from middle" rule for circular lines, maintaining the proper reference to the Circle Line in London, UK.
431-431: Simple but accurate translation.The translation "Ver también" is the correct way to translate "See Also" in Spanish.
osgeoweblate
force-pushed
the
weblate-postgis-workshop-index
branch
from
410125f to
d8c4729
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🔭 Outside diff range comments (1)
postgis-intro/sources/locale/es/LC_MESSAGES/upgrades.po (1)
57-216: 🛠️ Refactor suggestionMany translations still missing in Spanish version.
Unlike the Chinese version which has more complete translations, the Spanish version has many msgstr entries that remain empty (from line 57 onwards). Consider prioritizing the completion of these translations to provide a more comprehensive Spanish localization.
🧹 Nitpick comments (5)
postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/postgis-functions.po (1)
133-133: Note: Several functions remain untranslated.There are still several functions with empty translations in this file, including ST_Perimeter, ST_NumPoints, ST_Distance, ST_DWithin, ST_Intersects, ST_Contains, and ST_Crosses. Consider translating these in a future update to improve the completeness of the Chinese documentation.
Would you like me to help prepare translations for these missing items in a follow-up PR?
Also applies to: 141-141, 171-171, 181-181, 189-189, 199-199, 209-209
postgis-intro/sources/locale/es/LC_MESSAGES/topology.po (1)
24-24: Fix typo in translated textThere's a typo in the Spanish translation: "topogeomety" should be "topogeometry". The term appears correctly in the English source text but is misspelled in the translation.
-msgstr "PostGIS soporta las especificaciones SQL/MM SQL-MM 3 Topo-Geo y Topo-Net 3 a través de una extensión llamada **postgis_topology**. Puedes conocer todas las funciones y tipos que proporciona esta extensión en `Manual: PostGIS Topology <https://postgis.net/docs/Topology.html>`_. La extensión *postgis_topology* incluye otra clase de tipo espacial central, llamado **topogeometry**. Además del tipo espacial *topogeomety*, encontrará funciones para construir *topologías* y poblar topologías." +msgstr "PostGIS soporta las especificaciones SQL/MM SQL-MM 3 Topo-Geo y Topo-Net 3 a través de una extensión llamada **postgis_topology**. Puedes conocer todas las funciones y tipos que proporciona esta extensión en `Manual: PostGIS Topology <https://postgis.net/docs/Topology.html>`_. La extensión *postgis_topology* incluye otra clase de tipo espacial central, llamado **topogeometry**. Además del tipo espacial *topogeometry*, encontrará funciones para construir *topologías* y poblar topologías."postgis-intro/sources/locale/es/LC_MESSAGES/joins_exercises.po (1)
40-41: Maintain consistency in function name translations for SQL functions.There's inconsistency in how SQL function names are handled:
sumis translated tosumacountis kept in EnglishFor consistency, either keep all SQL function names in their original English form or translate all of them to Spanish.
Also applies to: 48-49
postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/upgrades.po (1)
175-223: Incomplete translations remain in the file.While significant progress has been made, several msgstr entries remain empty (lines 175-216). Consider completing these translations in a future update for a fully localized experience.
postgis-intro/sources/locale/es/LC_MESSAGES/advanced_geometry_construction.po (1)
27-27: Translation accuracy verification.The Spanish translation "Construcción de Geometrías" is an accurate representation of "Advanced Geometry Constructions", though it omits the "Advanced" qualifier. Consider changing to "Construcción Avanzada de Geometrías" for completeness.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (38)
postgis-intro/sources/locale/es/LC_MESSAGES/3d.po(1 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/about_data.po(1 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/advanced_geometry_construction.po(7 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/backup.po(1 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/creating_db.po(5 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/equality.po(7 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/geography.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/geography_exercises.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/geometries.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/geometries_exercises.po(7 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/geometry_returning.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/geometry_returning_exercises.po(4 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/introduction.po(1 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/joins.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/joins_advanced.po(1 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/joins_exercises.po(4 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/license.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/postgis-functions.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/projection_exercises.po(6 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/schemas.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/simple_sql.po(7 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/simple_sql_exercises.po(8 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/spatial_relationships_exercises.po(5 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/topology.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/upgrades.po(3 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/validity.po(4 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/welcome.po(1 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/3d.po(4 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/advanced_geometry_construction.po(1 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/clusterindex.po(8 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/equality.po(1 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/geography_exercises.po(2 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/history_tracking.po(6 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/index.po(2 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/license.po(2 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/postgis-functions.po(5 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/spatial_relationships.po(2 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/upgrades.po(7 hunks)
🚧 Files skipped from review as they are similar to previous changes (25)
- postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/index.po
- postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/history_tracking.po
- postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/3d.po
- postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/spatial_relationships.po
- postgis-intro/sources/locale/es/LC_MESSAGES/geography.po
- postgis-intro/sources/locale/es/LC_MESSAGES/equality.po
- postgis-intro/sources/locale/es/LC_MESSAGES/projection_exercises.po
- postgis-intro/sources/locale/es/LC_MESSAGES/simple_sql.po
- postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/equality.po
- postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/license.po
- postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/advanced_geometry_construction.po
- postgis-intro/sources/locale/es/LC_MESSAGES/license.po
- postgis-intro/sources/locale/es/LC_MESSAGES/about_data.po
- postgis-intro/sources/locale/es/LC_MESSAGES/joins.po
- postgis-intro/sources/locale/es/LC_MESSAGES/geometries_exercises.po
- postgis-intro/sources/locale/es/LC_MESSAGES/schemas.po
- postgis-intro/sources/locale/es/LC_MESSAGES/geometry_returning_exercises.po
- postgis-intro/sources/locale/es/LC_MESSAGES/backup.po
- postgis-intro/sources/locale/es/LC_MESSAGES/creating_db.po
- postgis-intro/sources/locale/es/LC_MESSAGES/geometry_returning.po
- postgis-intro/sources/locale/es/LC_MESSAGES/joins_advanced.po
- postgis-intro/sources/locale/es/LC_MESSAGES/spatial_relationships_exercises.po
- postgis-intro/sources/locale/es/LC_MESSAGES/geometries.po
- postgis-intro/sources/locale/es/LC_MESSAGES/simple_sql_exercises.po
- postgis-intro/sources/locale/es/LC_MESSAGES/geography_exercises.po
🔇 Additional comments (78)
postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/postgis-functions.po (6)
5-5: Metadata updates look correct.The updated translator information, revision date (March 27, 2025), and Weblate generator version are consistent with the PR's translation update workflow.
Also applies to: 11-12, 20-20
57-58: Translation for ST_SetSRID is thorough and accurate.The Chinese translation properly explains that the function updates the spatial reference identifier without altering coordinates, and describes its use case for geometries without defined spatial references.
69-70: Good translation for ST_Expand.The translation clearly communicates the function's purpose in creating an expanded bounding box and its application for indexed searches.
82-82: Clear and concise translation for ST_AsText.The translation accurately describes the function's purpose of returning a human-readable text format.
90-90: Complete translation for ST_AsGML.The translation correctly conveys that the function returns geometry in the OGC standard GML format, maintaining the term reference syntax.
123-123: Good translation for ST_Length.The translation accurately describes the function as returning length values in the units of the spatial reference system.
postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/geography_exercises.po (7)
6-6: Metadata updates look good.The updated translator information and revision date follow proper i18n formatting standards.
Also applies to: 12-13
86-86: Translation accurately captures the original question.Good addition of the translation for the distance question between New York and Seattle, preserving both the core question and the units inquiry.
90-91: Technical coordinates properly preserved in translation.The translation correctly maintains the exact coordinate values while adding appropriate Chinese context.
95-95: Street length calculation question effectively translated.The translation maintains the technical accuracy while slightly rephrasing to "How to calculate..." which works well in Chinese.
100-102: Technical details correctly preserved in UTM explanation.The translation properly maintains the important numerical values (10418904.717, 0.02%) while providing clear context in Chinese about the UTM projection's properties.
107-108: Geometry vs. Geography intersection question well translated.The translation effectively communicates the technical distinction between the coordinate systems while maintaining the question format.
113-115: Critical technical distinction properly preserved.The translation correctly maintains the important technical distinction between the below/above behavior in different coordinate systems, which is essential for understanding the concept.
postgis-intro/sources/locale/es/LC_MESSAGES/topology.po (3)
6-6: Translator credit looks goodThe addition of the new translator credit with name, email, and year appears correctly formatted.
8-8: Translation metadata properly formattedThe metadata block is well-structured with all required fields: project version, bug reporting information, creation/revision dates, translator details, language information, and encoding specifications. The revision date (March 27, 2025) and language team URL are up-to-date.
12-12: Term translation looks goodThe Spanish translation "Topología" for "Topology" is correct and properly accented.
postgis-intro/sources/locale/es/LC_MESSAGES/welcome.po (9)
7-9: Updated translator information and metadata look good.The addition of a new translator credit for Paulo Cesar and the updated metadata (PO-Revision-Date) properly document the changes made to this file in 2025.
17-21: Well-translated workshop conventions section.The translation effectively conveys the meaning of the original text while using natural Spanish phrasing. The translation of "Workshop Conventions" as "Convenciones usadas en el Taller" adds helpful context in Spanish.
25-38: Directions section accurately translated.Good choice of terminology with "Indicaciones" for "Directions" and "Pulse" for "Click" - these are standard UI terms in Spanish. The bold font explanation and example are correctly translated while maintaining the formatting instructions.
46-50: Code section translations are accurate.The translations correctly explain how SQL examples will be displayed and how they can be used in the query window or command line interface.
54-62: Notes section well translated including the idiom.The translation preserves both the technical explanation of what notes are used for and correctly translates the idiomatic example about apples and doctors.
70-74: Functions section properly translated.The translation correctly explains how function names are rendered in the text and accurately translates the example of ST_Touches function behavior.
78-86: Files, Tables and Column Names section properly translated.Correct translation of technical terms with proper Spanish capitalization conventions, maintaining the fixed-width font instruction and example.
90-98: Menus and Form elements section translated effectively.Good translation of UI terminology, with "Menus/submenus and form elements" translated to "Los menús/submenús y los elementos de formulario", preserving the technical meaning while using natural Spanish phrasing.
102-106: Workflow section expertly translated.The translation of this complex paragraph is excellent, accurately conveying all the nuances of the section progression, exercises, and "Things To Try" challenges while maintaining natural Spanish flow.
postgis-intro/sources/locale/es/LC_MESSAGES/joins_exercises.po (1)
53-53: Maintain consistency in function name translations.There's inconsistency in how PostGIS function names are handled in translations:
- Some function names are kept in English (ST_Area, ST_AsText, ST_DWithin)
- Some function names are translated to Spanish (ST_Contiene, ST_Distancia)
- Some parameters are translated to Spanish (geometría, radio)
- Some parameters are kept in English (geometry in ST_AsText)
Per previous review feedback, PostGIS function names should remain unchanged in translations to maintain consistency with official documentation and avoid confusion.
Please update the following translations to maintain the original function names:
- ":command:`ST_Contiene(geometría A, geometría B)` devuelve verdadero si la geometría A contiene a la geometría B" + ":command:`ST_Contains(geometría A, geometría B)` devuelve verdadero si la geometría A contiene a la geometría B"- ":command:`ST_Distancia(geometría A, geometría B)` devuelve la distancia mínima entre la geometría A y la geometría B" + ":command:`ST_Distance(geometría A, geometría B)` devuelve la distancia mínima entre la geometría A y la geometría B"Also, consider maintaining consistency in parameter translations (either all "geometry" or all "geometría").
Also applies to: 58-59, 66-67, 74-75, 82-83
postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/upgrades.po (4)
5-5: Metadata update looks good.The addition of the new translator "Wangdapeng" with proper email and year 2025 matches the other metadata changes in this file.
19-20: Configuration settings updated correctly.The Plural-Forms and X-Generator fields have been properly specified for Chinese (Simplified) with the correct plural rule.
24-24: The Chinese translations look complete and accurate.The added translations in Simplified Chinese are well-formulated and accurately convey the technical information about PostgreSQL and PostGIS upgrades. Several previously untranslated strings now have proper translations.
Also applies to: 33-35, 45-47, 51-51, 55-55, 59-59, 68-70, 78-79, 83-83, 89-89, 93-93, 97-97, 101-101, 112-115, 128-129, 135-135, 139-139, 143-143, 156-158, 164-164, 171-171
11-14:✅ Verification successful
Verify the date in PO-Revision-Date field.
The revision date is set to 2025-03-27, which appears to be a future date. This might be correct if your system clock is set to 2025, but please verify this is intentional.
🏁 Script executed:
#!/bin/bash # Check current date to compare with the future-dated revision date echo "Checking other .po files for similar date patterns..." grep -r "PO-Revision-Date: 2025" --include="*.po" ./postgis-intro/sources/locale/Length of output: 6707
Revision Date Confirmed as Intended
- The system clock is correctly set to March 27, 2025.
- The revision date ("2025-03-27 06:47+0000") in this file aligns with both the current system date and similar entries in other locale files.
- No changes are necessary.
postgis-intro/sources/locale/es/LC_MESSAGES/upgrades.po (4)
6-6: Metadata update looks good.The addition of "Paulo Cesar" as the translator with proper email and year 2025 is consistent with the other metadata changes in this file.
12-16: Verify the date in PO-Revision-Date field.Similar to the Chinese translation file, the revision date is set to 2025-03-27, which appears to be a future date. Please verify this is intentional across all translation files.
20-21: Configuration settings updated correctly.The Plural-Forms and X-Generator fields have been properly specified for Spanish with the correct plural rule (nplurals=2; plural=n != 1).
26-26: The Spanish translations are accurate but incomplete.The added Spanish translations accurately convey the technical information for the sections that have been translated. The translation of "Software Upgrades" and the paragraphs about PostGIS and PostgreSQL relationships are well done.
Also applies to: 35-39, 49-53
postgis-intro/sources/locale/es/LC_MESSAGES/postgis-functions.po (6)
6-6: Metadata updates look appropriate for Spanish localization.The translator information, revision date, language team, and plural forms have been properly updated to reflect the Spanish localization project. The URL for the translation project is also correctly formatted.
Also applies to: 12-16, 20-21
26-26: Section headers have been appropriately translated.The translations for "Anexo A: Funciones de PostGIS", "Constructores", and "Salidas" are accurate Spanish equivalents for the original English terms.
Also applies to: 30-30, 76-76
34-34: Command names correctly preserved in translations.The function names (ST_MakePoint, ST_GeomFromText, etc.) have been correctly kept untranslated in the Spanish version, as these are command names that should remain consistent across languages.
Also applies to: 46-46, 80-80, 88-88, 96-96
41-42: Function description accurately translated.The translation of the ST_MakePoint description accurately conveys the original meaning about coordinate order (longitude then latitude) in Spanish.
48-201: Multiple function descriptions remain untranslated.Many function descriptions still have empty translations (empty msgstr entries), including ST_GeomFromText, ST_SetSRID, ST_Expand, ST_AsText, and others. This appears to be an incremental translation update with more work to be completed in the future.
12-12:✅ Verification successful
Verify the future revision date.
The PO-Revision-Date is set to March 27, 2025, which is in the future. While this may be intentional for scheduled updates, it might be worth confirming if this date is correct.
🏁 Script executed:
#!/bin/bash # Check the current date to compare with the revision date in the file echo "Current date for reference: $(date)" echo "Revision date in file: 2025-03-27" echo "Checking other PO files for consistent revision dates..." grep -r "PO-Revision-Date:" --include="*.po" . | head -n 10Length of output: 1442
Attention: PO-Revision-Date Verification
After running the verification script, the current system date ("Thu Mar 27 06:51:34 UTC 2025") closely matches the revision date in the file ("2025-03-27 06:47+0000"). This indicates that the date is not erroneously set in the future. It appears the timestamp was updated as expected—likely reflecting the current update cycle. Please confirm that this behavior is intentional, especially considering other
.pofiles show either placeholders or different dates.postgis-intro/sources/locale/es/LC_MESSAGES/validity.po (11)
8-8: Updated translator information looks goodThe addition of Paulo Cesar as a new translator for 2025 is properly formatted and consistent with the translation team structure.
14-15: Metadata updates are appropriateThe revision date and translator information have been correctly updated to reflect the latest changes by Paulo Cesar.
37-40: Well-translated technical explanationThe Spanish translation accurately captures the meaning of the original text about topology exceptions, using appropriate punctuation and technical terminology in Spanish.
43-44: Good addition of missing translationThe previously empty translation for "What is Validity" has been appropriately translated to "¿Qué es la Validez?" with proper Spanish question marks.
52-54: Clear technical translationThe translation about polygon validity maintains technical accuracy while being natural in Spanish.
66-66: Concise translation of rule"Los anillos del polígono deben cerrarse" is an excellent translation for "Polygon rings must close."
80-80: Precise technical translation with clarificationThe translation adds helpful clarification in parentheses to explain what "self-intersect" means, which improves understanding for Spanish readers.
88-88: Accurate translation of spatial constraintThe translation correctly conveys the rule that elements of multi-polygons cannot touch each other.
109-114: Well-structured complex sentence translationThe translation of this complex technical explanation about algorithms and structure maintains clarity while properly conveying the technical concepts.
119-120: Clear translation with proper Spanish phrasingThe translation "He aquí un ejemplo del por qué la estructura importa" maintains the meaning while using a natural Spanish construction.
133-137: Technical accuracy in translationThe translation maintains technical accuracy when describing the figure-eight shape and its representation, using appropriate Spanish terminology for geometric concepts.
postgis-intro/sources/locale/es/LC_MESSAGES/introduction.po (3)
9-9: Updated translator information looks goodThe addition of Paulo Cesar as a new translator for 2025 is properly formatted and consistent with the translation team structure.
15-16: Metadata updates are appropriateThe revision date and translator information have been correctly updated to reflect the latest changes by Paulo Cesar.
876-878: Removed fuzzy mark from translationThe translation for "Dbt" has been properly finalized by removing the fuzzy mark that would have been present in the original file.
postgis-intro/sources/locale/es/LC_MESSAGES/3d.po (7)
6-8: Updated translator and metadata informationThe addition of Paulo Cesar as translator and all the metadata updates are properly formatted according to PO file standards. The complete metadata block includes all necessary fields with correct formatting.
12-12: Consistent 3-D terminologyThe Spanish translation maintains the hyphenated format "3-D" consistent with the original English text, which is appropriate for technical documentation.
16-16: Properly translated heading"Geometrías 3-D" is an accurate and natural translation of "3-D Geometries".
20-20: Well-translated complex technical sentenceThe translation accurately conveys the technical information about dimensional geometry while maintaining natural Spanish phrasing.
84-84: Well-translated technical term"Funciones 3D" is an appropriate translation of "3-D Functions" and follows Spanish technical convention by dropping the hyphen.
128-128: Appropriate heading translation"Índices N-D" correctly translates "N-D Indexes" maintaining the technical abbreviation format.
132-132: Clear translation of technical adviceThe translation about data distribution and multi-dimensional indexing conveys the technical recommendation clearly.
postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/clusterindex.po (9)
5-5: Updated translator informationThe translator information has been updated from Chen to Wangdapeng with an appropriate email address.
11-12: Updated metadata informationThe revision date and translator information have been correctly updated to reflect the latest changes.
20-20: Updated generation tool versionThe X-Generator field has been updated from an older version to Weblate 5.4.3.
24-24: Concise Chinese translation"索引聚类" is an excellent, concise translation of "Clustering on Indices" that maintains the technical meaning.
33-35: Well-structured technical explanationThe Chinese translation effectively explains database performance limitations related to disk access, maintaining the technical accuracy while using natural Chinese phrasing.
50-51: Clear explanation with technical termThe translation maintains the technical term "聚类" (clustering) in quotes while providing a clear explanation of the concept in Chinese.
104-104: Good translation of comparison heading"磁盘存储 vs 内存/固态存储" appropriately translates "Disk Versus Memory/SSD" using the abbreviated "vs" which is commonly understood in technical contexts.
129-130: Elegant translation using Chinese quotation marksThe translation uses proper Chinese quotation marks「」for the concepts of "near each other" which makes the text more readable for Chinese users.
166-167: Technical comparison with appropriate quotation marksThe translation uses Chinese quotation marks for the technical comparison between different index types, making it more readable for the target audience.
postgis-intro/sources/locale/es/LC_MESSAGES/advanced_geometry_construction.po (8)
7-7: Metadata updates look good.The translator information, revision date, and generator version have been appropriately updated to reflect the new contributor and current tooling.
Also applies to: 13-14, 22-22
34-35: Technical translation is well-executed.The Spanish translations accurately preserve the technical meaning of the original text while maintaining readability. Code elements like
nyc_subway_stationsandroutesare correctly preserved with their original formatting.Also applies to: 44-47, 59-61, 70-74, 81-82
101-104: Links and technical references are properly maintained.The translation correctly preserves links to technical documentation while translating the surrounding text appropriately. For example, PL/PgSQL links remain intact while the descriptive text is translated to Spanish.
Also applies to: 109-110, 117-118, 125-126, 134-137
162-167: SQL function references accurately translated.Technical SQL terms like strpos, array_append, and @> are properly maintained in their original form, while the explanatory text is well translated to Spanish. This maintains the technical accuracy while making the content accessible to Spanish speakers.
215-220: PostGIS function reference correctly preserved.The translation properly maintains the PostGIS function reference to
ST_MakeLine <http://postgis.net/docs/ST_MakeLine.html>while translating the surrounding explanatory text.
275-277: Good cultural adaptation in directional references.The translation adds helpful clarification by including "septentrionales" and "meridionales" alongside "norte" and "sur", which improves understanding for Spanish-speaking users who may be more familiar with these geographic terms.
305-307: Geographic context preserved correctly.The translation maintains the geographical example of the "Circle Line in London, UK" while translating the surrounding explanatory text, preserving the important context for Spanish-speaking users.
314-450: Remaining untranslated content.There are several sections from line 314 onward that remain untranslated. While this PR shows significant progress in translation, these remaining sections should be addressed in future updates for completeness.
Consider creating a follow-up task to translate the remaining sections of this document.
osgeoweblate
force-pushed
the
weblate-postgis-workshop-index
branch
from
d8c4729 to
bd41a6d
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (2)
postgis-intro/sources/locale/es/LC_MESSAGES/3d.po (1)
28-28:⚠️ Potential issueMissing PointZ type in translation
The translation is missing the PointZ type that's mentioned in the English original. This was flagged in a previous review but still needs to be fixed.
-Point (un tipo 2-D ) es complementada por los tipos PointM y PointZM . +Point (un tipo 2-D) es complementada por los tipos PointZ, PointM y PointZM.postgis-intro/sources/locale/es/LC_MESSAGES/equality.po (1)
125-125:⚠️ Potential issueSphinx markup incorrectly translated
The Sphinx documentation markup
:command:has been incorrectly translated to:comando:. Documentation markup tags should not be translated as they are part of the system syntax.-proporciona el operador de límites iguales, :comando:`~=`. Este operador +proporciona el operador de límites iguales, :command:`~=`. Este operador
🧹 Nitpick comments (4)
postgis-intro/sources/locale/es/LC_MESSAGES/advanced_geometry_construction.po (1)
311-450: Multiple untranslated sections remain in the document.I notice that from line 311 onward, there are several sections that remain untranslated (empty msgstr strings). These include important content about:
- Finding distinct routes
- PostgreSQL array functions
- Building tables for stations on routes
- Finding center points and end stations
- Creating route lines
- Example visualizations and edge cases
Consider completing these translations to provide a fully localized experience.
Would you like assistance in translating these remaining sections to maintain consistency with the excellent quality of the translations provided so far?
postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/geometries_exercises.po (1)
32-32: Confirm double-colon usage for consistency.
Here,::command:is used instead of:command:. Confirm this matches your documentation formatting guidelines so that the rendered output is as expected.postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/spatial_relationships_exercises.po (1)
32-32: Double-colon notation check.
As with the other file, verify that using::command:is deliberate and consistent across all translations.postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/introduction.po (1)
63-63: Formatting issue in Markdown syntaxThere's an extra space between the first asterisk and the text in the bold syntax that should be removed for proper Markdown formatting.
-** 空间数据类型** 用于表示点、线、面等几何形状; +**空间数据类型** 用于表示点、线、面等几何形状;
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (47)
postgis-intro/sources/locale/es/LC_MESSAGES/3d.po(1 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/about_data.po(1 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/advanced_geometry_construction.po(7 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/backup.po(1 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/creating_db.po(5 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/equality.po(7 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/geography.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/geography_exercises.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/geometries.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/geometries_exercises.po(7 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/geometry_returning.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/geometry_returning_exercises.po(4 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/introduction.po(1 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/joins.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/joins_advanced.po(1 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/joins_exercises.po(4 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/license.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/postgis-functions.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/projection_exercises.po(6 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/schemas.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/simple_sql.po(7 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/simple_sql_exercises.po(8 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/spatial_relationships_exercises.po(5 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/topology.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/upgrades.po(3 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/validity.po(4 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/welcome.po(1 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/3d.po(4 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/about_data.po(2 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/advanced_geometry_construction.po(2 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/clusterindex.po(8 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/equality.po(1 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/geography_exercises.po(2 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/geometries_exercises.po(2 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/history_tracking.po(6 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/index.po(2 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/introduction.po(2 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/joins.po(3 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/license.po(2 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/loading_data.po(2 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/postgis-functions.po(6 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/projection_exercises.po(2 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/simple_sql.po(2 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/simple_sql_exercises.po(3 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/spatial_relationships.po(3 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/spatial_relationships_exercises.po(2 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/upgrades.po(7 hunks)
🚧 Files skipped from review as they are similar to previous changes (28)
- postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/geography_exercises.po
- postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/spatial_relationships.po
- postgis-intro/sources/locale/es/LC_MESSAGES/geography.po
- postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/history_tracking.po
- postgis-intro/sources/locale/es/LC_MESSAGES/validity.po
- postgis-intro/sources/locale/es/LC_MESSAGES/introduction.po
- postgis-intro/sources/locale/es/LC_MESSAGES/license.po
- postgis-intro/sources/locale/es/LC_MESSAGES/creating_db.po
- postgis-intro/sources/locale/es/LC_MESSAGES/about_data.po
- postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/3d.po
- postgis-intro/sources/locale/es/LC_MESSAGES/simple_sql.po
- postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/license.po
- postgis-intro/sources/locale/es/LC_MESSAGES/spatial_relationships_exercises.po
- postgis-intro/sources/locale/es/LC_MESSAGES/geometry_returning.po
- postgis-intro/sources/locale/es/LC_MESSAGES/schemas.po
- postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/index.po
- postgis-intro/sources/locale/es/LC_MESSAGES/projection_exercises.po
- postgis-intro/sources/locale/es/LC_MESSAGES/geometries.po
- postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/equality.po
- postgis-intro/sources/locale/es/LC_MESSAGES/topology.po
- postgis-intro/sources/locale/es/LC_MESSAGES/joins_advanced.po
- postgis-intro/sources/locale/es/LC_MESSAGES/backup.po
- postgis-intro/sources/locale/es/LC_MESSAGES/geometries_exercises.po
- postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/postgis-functions.po
- postgis-intro/sources/locale/es/LC_MESSAGES/simple_sql_exercises.po
- postgis-intro/sources/locale/es/LC_MESSAGES/joins_exercises.po
- postgis-intro/sources/locale/es/LC_MESSAGES/joins.po
- postgis-intro/sources/locale/es/LC_MESSAGES/geometry_returning_exercises.po
🔇 Additional comments (102)
postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/joins.po (4)
5-5: LGTM! Updated copyright year for translatorThe copyright line has been properly updated to include 2025, extending Wangdapeng's contribution period from just 2024 to include 2025 as well.
11-11: LGTM! Updated PO-Revision-DateThe PO-Revision-Date has been updated to March 27, 2025, correctly reflecting the latest revision of this translation file.
189-190: LGTM! Improved ST_Intersects function descriptionThe translation for the ST_Intersects function has been refined to more clearly explain that it returns TRUE when geometries share any portion of space and FALSE when geometries are disjoint. This improves understanding for Chinese-speaking users.
208-209: LGTM! Added clear translation for sum() functionThe translation for the PostgreSQL aggregate function sum(expression) has been properly added, explaining that it calculates the sum of values in a set of records. This helps Chinese-speaking users better understand this commonly used SQL function.
postgis-intro/sources/locale/es/LC_MESSAGES/postgis-functions.po (7)
6-6: Appropriate metadata updates for localization file.The metadata updates correctly identify Paulo Cesar as the translator with proper contact information, revision date, and Spanish language team details. The plural forms rule (nplurals=2; plural=n != 1) is correctly set for Spanish language standards.
Also applies to: 12-16, 20-21
26-26: Accurate translation of section title."Appendix A: PostGIS Functions" has been correctly translated to "Anexo A: Funciones de PostGIS", maintaining both meaning and formatting.
30-30: Accurate translation of technical term."Constructors" has been appropriately translated to "Constructores" in Spanish.
34-34: Correctly preserved technical function names.The function names (ST_MakePoint, ST_GeomFromText, ST_AsText, ST_AsGML, ST_AsGeoJSON) have been appropriately left untranslated as these are technical terms that should remain consistent across languages.
Also applies to: 46-46, 80-80, 88-88, 96-96
41-42: Accurate translation of function description.The description for ST_MakePoint has been correctly translated to Spanish, maintaining the important technical note about coordinate order (longitude then latitude).
76-76: Accurate translation of section title."Outputs" has been correctly translated to "Salidas" in Spanish.
48-212: Note: Incomplete translations in the file.Many strings in this file remain untranslated (empty msgstr values), which suggests this is a work in progress. This is normal in localization projects where translations are added incrementally. Future contributions can address the remaining untranslated strings.
postgis-intro/sources/locale/es/LC_MESSAGES/advanced_geometry_construction.po (8)
7-7: Metadata properly updated with new translator information.The file has been correctly updated with the new translator information (Paulo Cesar), a current revision date (March 18, 2025), and the latest Weblate generator version (5.4.3).
Also applies to: 13-14, 22-22
27-27: Good translation of the main title.The translation of "Advanced Geometry Constructions" to "Construcción de Geometrías" accurately conveys the meaning in Spanish while maintaining the technical nature of the content.
34-35: Accurate translation of technical content.The Spanish translation accurately preserves the technical terminology (
nyc_subway_stations) while providing a natural-sounding translation that maintains the meaning of the original text.Also applies to: 44-47
51-51: Well-structured translations for complex technical explanations.These translations effectively communicate the technical challenges of working with the subway station data. They maintain clarity while explaining complex concepts about route identification and station ordering.
Also applies to: 59-61, 70-74, 81-82
85-85: Consistent technical terminology in translations.The translations consistently preserve technical terms (like "gid", "PL/PgSQL", etc.) while providing fluent Spanish text for the explanatory content. This maintains the technical accuracy of the documentation.
Also applies to: 93-93, 101-104, 109-110, 117-118, 125-126
134-137: Excellent translations of PostgreSQL-specific technical content.These translations successfully convey complex PostgreSQL concepts like CTEs, arrays, and operators while maintaining technical accuracy. The Spanish text flows naturally and would be clear to Spanish-speaking PostgreSQL users.
Also applies to: 149-151, 162-167, 174-175, 183-185, 191-192, 201-205
215-220: Thorough and accurate translations of spatial concepts.The translations effectively communicate spatial concepts and the PostgreSQL/PostGIS methodologies for handling them. The translations for directional terms (like "northerly/southerly") are appropriately contextual in Spanish.
Also applies to: 224-224, 228-228, 232-232, 239-240, 248-250, 257-259, 266-267, 275-277
286-289: Precise translation of technical edge cases.The translations accurately capture the nuances of the spatial analysis approach, including potential edge cases like circular routes. Technical terminology is preserved appropriately.
Also applies to: 296-297, 305-307
postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/advanced_geometry_construction.po (4)
4-4: Metadata updates look good.The file metadata has been properly updated with the new translator information (Wangdapeng), updated revision date (March 2025), team URL, and Weblate version (5.4.3).
Also applies to: 10-13, 18-19
23-23: New Chinese translations have been added correctly.The PR has successfully added Chinese translations for multiple sections of the "Advanced Geometry Construction" chapter. Technical terms, code examples, and formatting elements like backticks have been preserved appropriately. The translator has effectively broken down longer sentences into multiple lines for better readability.
Also applies to: 27-28, 33-34, 38-38, 43-44, 48-49, 53-54, 58-58, 62-62, 66-67, 71-71, 76-77, 82-83, 88-89, 93-93, 97-98, 103-107, 111-111, 116-117, 121-121, 126-128, 133-135, 139-139, 143-143, 147-147, 151-151, 155-156, 160-161, 265-265
166-262: Note: Several sections still require translation.Multiple sections in the latter part of the document (lines 166-262) have msgid entries but no corresponding msgstr translations. While this isn't a problem with the current changes (which are all correct), it indicates that the translation of this document is not yet complete.
This is just an observation and doesn't require any changes to the current PR, which is adding valuable translations to previously untranslated content.
269-281: "See Also" section links need translation.The "See Also" section header has been translated, but the links in this section (PostgreSQL Arrays, Array Functions, Recursive Common TABLE Expressions, and PostGIS ST_MakeLine) don't have corresponding translations yet.
While this doesn't affect the functionality of the links, consider translating the link descriptions in a future update for consistency with the rest of the document.
postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/projection_exercises.po (2)
4-4: LGTM: Translator metadata updated.The translator metadata has been appropriately updated to include 2025 alongside 2024, reflecting continued contributions from the translator in the current year.
10-10: LGTM: PO-Revision-Date updated.The revision date has been updated to reflect the most recent translation update (March 27, 2025), which is critical for tracking translation versions.
postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/simple_sql.po (3)
5-5: New translator added for 2025.A new translator (Wangdapeng) has been added for the year 2025. This is a standard metadata update and ensures proper attribution for translation work.
11-12: Updated metadata for translation file.The revision date has been updated to March 27, 2025, the last translator has been changed to Wangdapeng, and the Weblate generator version has been updated to 5.4.3. These changes reflect proper maintenance of translation metadata.
Also applies to: 20-20
171-172: Improved translation clarity for PostgreSQL function.The translation for
avg(expression)function has been refined to be more natural in Chinese. The new wording improves readability while maintaining the technical meaning of the PostgreSQL aggregate function.postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/simple_sql_exercises.po (6)
7-7: Updated translator attribution to include 2025.The translator attribution for Wangdapeng has been updated to include 2025 alongside 2024, properly reflecting their continued contribution to the translation.
13-13: Updated revision date.The PO-Revision-Date has been updated to March 27, 2025, reflecting the date of the latest translation updates.
124-126: Enhanced borough name translation with English equivalents.The translation has been improved by including both Chinese translations and English original names in parentheses for New York boroughs. This provides valuable context for Chinese readers who may need to recognize the English names as well.
195-196: Improved translation formatting for avg() function.The translation for the PostgreSQL aggregate function
avg()has been improved with better sentence structure in Chinese.
202-203: Improved translation for count() function.The translation for the PostgreSQL
count()function has been refined for better clarity in Chinese.
209-210: Improved translation for sum() function.The translation for the PostgreSQL
sum()function has been refined to more clearly explain its purpose in Chinese.postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/about_data.po (3)
5-5: New translator added for 2025.A new translator (Wangdapeng) has been added for the year 2025. This properly attributes recent translation work.
11-12: Updated translation metadata.The revision date has been updated to March 27, 2025, the last translator information has been updated to Wangdapeng, and the Weblate generator version has been updated to 5.4.3. These are standard maintenance updates for translation files.
Also applies to: 20-20
123-125: Improved translation of borough names with English equivalents.The translation for New York borough names has been enhanced by including both Chinese translations and English names in parentheses. This provides better context for Chinese readers and maintains consistency with similar changes in other files.
postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/geometries_exercises.po (2)
11-11: PO-Revision-Date update looks good.
No issues are evident with the date change; it follows standard.pofile practices.
36-36: Translation refinement approved.
The updated phrasing provides a clearer explanation of returning the total number of records.postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/spatial_relationships_exercises.po (3)
5-5: Updated translator attribution appears correct.
No concerns with adding the 2025 reference.
11-11: PO-Revision-Date update is valid.
Date change is standard for.pofile revisions.
36-36: Improved clarity of 'count(expression)' translation.
The updated text accurately describes returning the total number of entries.postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/loading_data.po (5)
5-5: Translator header updated.
Adding the new translator/year is consistent with project guidelines.
11-11: PO-Revision-Date updated successfully.
This change aligns.pometadata with the new date.
12-12: Last-Translator field updated correctly.
No issues found with the change.
20-20: X-Generator version bump is acceptable.
Reflecting the updated Weblate version is standard practice.
111-112: Refined translation for HomeBrew and ogr2ogr.
The new phrasing is concise and maintains clarity.postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/upgrades.po (32)
5-5: Added translator info for 2025.
No concerns; this aligns with the usual.pofile convention.
11-11: PO-Revision-Date updated.
Standard metadata update for the revision date.
12-12: Last-Translator updated.
Correctly reflects the new translator’s contact.
13-14: Language-Team field revised.
Points to the correct Weblate project link for Simplified Chinese.
19-19: Plural-Forms updated.
Matches the typical rule for Chinese (1 plural form).
20-20: X-Generator version change.
Indicates the use of Weblate 5.4.3, which is appropriate.
24-24: New translation for “Software Upgrades.”
“软件升级” is succinct and clear.
33-35: Refined explanation of dual-version PostGIS installation.
The text accurately conveys that both PostgreSQL and PostGIS versions coexist.
45-47: Clarified description of available version pairs.
The text succinctly reflects the role of Linux packagers in providing multiple version options.
51-52: Slightly reworded upgrade consideration.
The updated text concisely describes the approach to component-based upgrades.
57-57: “Upgrading PostgreSQL” heading translation.
Matches the overall style of other section headings.
60-60: Translated “There are two kinds of PostgreSQL upgrade scenarios.”
Appropriately matches the original meaning.
68-70: “Minor upgrade” explanation.
Accurately reflects that these upgrades fix bugs without adding new features.
78-80: “Major upgrade” explanation.
Correctly captures introduction of new features and behavior changes in major versions.
88-88: Minor PostgreSQL Upgrades heading translation.
Clear reflection of the original meaning.
90-90: Short description of minor upgrade steps.
Accurately states that no special process is needed other than installing new software and restarting.
98-98: Major PostgreSQL Upgrades heading translation.
Maintains consistency with the original heading structure.
102-102: Translated steps for major upgrades.
Reflects the two paths (Dump/Restore or pg_upgrade).
112-114: Dump/Restore process details.
The text clarifies the time cost and CPU demands of converting data to a neutral format.
128-130: Explained the need to match PostGIS versions.
Ensures that function definitions align properly when restoring the database.
136-136: Pg upgrade step uses new initdb.
Clear and consistent with official PostgreSQL documentation.
140-140: Stopping both servers before migration.
This is standard practice to avoid conflicting reads/writes during upgrade.
144-144: pg_upgrade usage from new installation.
Reminds the reader to ensure the binary is from the newer version.
148-148: Reference to documentation for full instructions.
Clear pointer to the official PostgreSQL website.
156-159: Explanation of pg_upgrade utility’s capabilities.
Accurate summary of how it handles internal system table changes.
165-165: Note on installing both Postgres versions for pg_upgrade.
Correctly emphasizes the need to have old and new side by side.
172-172: Step for installing matching PostGIS version.
Ensures the extension definitions remain compatible.
176-176: Initialize new PostgreSQL data area.
No concerns; standard procedure to prepare a fresh cluster.
182-182: Double-checking servers are off.
Crucial to avoid collisions during upgrade.
187-187: Using pg_upgrade from the new installation.
Matches recommended best practices for version transitions.
191-191: Completing pg_upgrade by running .sql files.
Straightforward final step if any migration scripts are generated.
197-197: Starting the new server after upgrade.
No issues; final step is correct and consistent with the standard process.postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/clusterindex.po (2)
5-5: Metadata updates look goodThe translator information, revision date, and generator version have been correctly updated to reflect the new contribution by Wangdapeng.
Also applies to: 11-12, 20-20
24-24: Well-structured Chinese translations addedThe translations appear accurate and maintain the technical meaning of the original text while being adapted to Chinese language patterns. The explanations of clustering, indexing, and performance considerations are clear and appropriate for technical documentation.
Also applies to: 32-35, 42-43, 50-51, 58-59, 65-65, 69-69, 77-77, 84-85, 89-89, 98-100, 104-104, 114-116, 129-130, 142-145, 156-157, 166-167, 178-179
postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/introduction.po (2)
7-7: Metadata updates look goodThe translator information, revision date, and generator version have been correctly updated to reflect the new contribution by Wangdapeng.
Also applies to: 13-14, 22-22
63-63: Good translation improvementThe modified translation changes "refers to shapes" to "used to represent geometric shapes," which enhances clarity and accuracy.
postgis-intro/sources/locale/es/LC_MESSAGES/3d.po (2)
6-8: Metadata updates look goodThe translator information, revision date, and generator version have been correctly updated to reflect the new contribution by Paulo Cesar.
11-165: Spanish translations for 3D concepts look goodThe translations for 3D geometry concepts, functions, and operations are accurate and maintain the technical context. The explanations match the original English text while being properly adapted for Spanish readers.
postgis-intro/sources/locale/es/LC_MESSAGES/equality.po (2)
6-6: Metadata updates look goodThe translator information, revision date, and generator version have been correctly updated to reflect the new contribution by Paulo Cesar.
Also applies to: 12-15, 20-21
26-26: Spanish translations for equality concepts are accurateThe translations for geometry equality concepts, functions, and examples are accurate and maintain the technical meaning. The explanations of exact equality, spatial equality, and equal bounds are well adapted for Spanish readers.
Also applies to: 35-39, 43-43, 47-47, 55-58, 68-73, 77-77, 86-89, 100-105, 109-109, 121-127, 139-145
postgis-intro/sources/locale/es/LC_MESSAGES/upgrades.po (5)
6-6: Translation metadata properly updated.The translator information has been updated to include Paulo Cesar as the translator with the correct email, reflecting the current contributor.
12-21: Translation metadata properly standardized.The metadata has been properly updated with:
- Current revision date (2025-03-27)
- Translator information
- Language team URL for Spanish translations via Weblate
- Explicit language specification (es)
- Proper plural forms definition
- Generator information
These changes ensure consistency across translation files and provide proper attribution.
26-26: Translation added for "Software Upgrades".Appropriate Spanish translation "Actualizaciones del Software" has been provided, which accurately conveys the meaning of the original text.
35-39: Translation added for the first paragraph of upgrades explanation.The Spanish translation accurately captures the relationship between PostGIS and PostgreSQL versions, properly maintaining the technical context of the original text.
49-53: Translation added for package management explanation.The Spanish translation correctly explains how package managers handle version pairs for PostgreSQL and PostGIS, maintaining the technical meaning of the original text.
postgis-intro/sources/locale/es/LC_MESSAGES/geography_exercises.po (6)
6-6: Translation metadata properly updated.The translator information has been updated to include Paulo Cesar as the translator with the correct email, reflecting the current contributor.
12-21: Translation metadata properly standardized.The metadata has been properly updated with:
- Current revision date (2025-03-27)
- Translator information
- Language team URL for Spanish translations via Weblate
- Explicit language specification (es)
- Proper plural forms definition
- Generator information
These changes ensure consistency across translation files and provide proper attribution.
26-26: Appropriate translation for "Geography Exercises".The title has been translated to "Ejercicios de Datos Tipo Geography", which clarifies that the exercises are related to the Geography data type specifically, providing more context than a literal translation would.
33-34: Translation added for functions reminder text.The Spanish translation accurately conveys the meaning of the original reminder about available functions, with appropriate punctuation in Spanish.
39-39: Consistent and accurate translations for function descriptions.The translations for the function descriptions:
- Maintain technical accuracy
- Preserve the command syntax
- Appropriately clarify the function's purpose in Spanish
- Use consistent terminology for geographic concepts
The consistent approach across all function descriptions makes the documentation more cohesive.
Also applies to: 43-43, 50-51, 58-59, 63-63, 70-71, 78-79
83-83: Remaining translations properly localized.All remaining translations:
- Maintain consistent formatting of code elements
- Preserve technical meaning
- Use appropriate Spanish terminology
- Keep proper punctuation according to Spanish conventions
The translations are accurate and maintain contextual integrity, particularly in the explanation of geometric vs. geographic intersection behavior.
Also applies to: 87-87, 91-91, 95-95, 99-99, 103-103, 108-109, 116-117, 124-125, 133-135, 142-143, 152-155
postgis-intro/sources/locale/es/LC_MESSAGES/welcome.po (4)
7-7: Translation metadata properly updated.The translator information has been updated to include Paulo Cesar as the translator with the correct email, reflecting the current contributor while preserving previous translator credits.
9-9: Metadata updated in a single line.The metadata has been updated with all necessary information (revision date, translator, language team, plural forms, etc.) in a single line rather than broken across multiple lines as in the other files. This is valid for PO files but differs from the formatting pattern seen in the other files reviewed.
17-17: Previously missing translations added.The previously untranslated sections have been completed with appropriate Spanish translations that:
- Accurately reflect the meaning of the original content
- Use proper Spanish terminology and conventions
- Maintain the instructional tone of the documentation
- Preserve formatting markers like bold text references
These additions significantly improve the completeness of the Spanish localization.
Also applies to: 25-25, 34-34, 38-38, 46-46, 54-54, 70-70, 74-74, 78-78, 90-90
21-21: Improved translations for longer paragraphs.The longer paragraphs have been translated with attention to:
- Natural Spanish language flow
- Preservation of technical meaning
- Proper adaptation of workshop-specific terminology
- Maintaining the instructional context
The translations show careful attention to providing a native-speaking experience rather than just literal translations.
Also applies to: 29-29, 50-50, 58-58, 82-82, 94-94, 106-106
| @@ -28,7 +28,7 @@ msgstr "这里提醒一下我们见过的一些功能。提示：它们应该对 | |||
|
|
|||
| #: ../../en/projection_exercises.rst:8 | |||
| msgid ":command:`sum(expression)` aggregate to return a sum for a set of records" | |||
| msgstr ":command:`sum(expression)`聚合函数用于对一组记录进行求和并返回总和" | |||
| msgstr "::command:`sum(expression)` 聚合函数，用于计算记录集合的数值总和" | |||
There was a problem hiding this comment.
Fix directive syntax - extra colon detected.
The translation has improved clarity by better explaining the aggregate function's purpose, but there's a formatting issue: ::command: uses two colons instead of one, which may cause rendering problems in the documentation.
-msgstr "::command:`sum(expression)` 聚合函数，用于计算记录集合的数值总和"
+msgstr ":command:`sum(expression)` 聚合函数，用于计算记录集合的数值总和"📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| msgstr "::command:`sum(expression)` 聚合函数，用于计算记录集合的数值总和" | |
| msgstr ":command:`sum(expression)` 聚合函数，用于计算记录集合的数值总和" |
Currently translated at 3.2% (2 of 61 strings) Translated using Weblate (Spanish) Currently translated at 100.0% (24 of 24 strings) Translated using Weblate (Spanish) Currently translated at 100.0% (21 of 21 strings) Translated using Weblate (Spanish) Currently translated at 51.7% (15 of 29 strings) Translated using Weblate (Spanish) Currently translated at 8.8% (3 of 34 strings) Translated using Weblate (Spanish) Currently translated at 100.0% (121 of 121 strings) Translated using Weblate (Spanish) Currently translated at 21.9% (9 of 41 strings) Translated using Weblate (Spanish) Currently translated at 21.4% (6 of 28 strings) Translated using Weblate (Spanish) Currently translated at 16.9% (9 of 53 strings) Translated using Weblate (Spanish) Currently translated at 47.0% (16 of 34 strings) Translated using Weblate (Spanish) Currently translated at 28.5% (8 of 28 strings) Translated using Weblate (Spanish) Currently translated at 23.3% (7 of 30 strings) Translated using Weblate (Spanish) Currently translated at 58.6% (34 of 58 strings) Translated using Weblate (Spanish) Currently translated at 32.7% (19 of 58 strings) Translated using Weblate (Spanish) Currently translated at 2.7% (2 of 74 strings) Translated using Weblate (Spanish) Currently translated at 3.4% (2 of 58 strings) Translated using Weblate (Spanish) Currently translated at 100.0% (43 of 43 strings) Translated using Weblate (Spanish) Currently translated at 100.0% (23 of 23 strings) Translated using Weblate (Spanish) Currently translated at 2.2% (3 of 133 strings) Translated using Weblate (Spanish) Currently translated at 4.7% (1 of 21 strings) Translated using Weblate (Spanish) Currently translated at 31.0% (9 of 29 strings) Translated using Weblate (Spanish) Currently translated at 75.5% (71 of 94 strings) Translated using Weblate (Spanish) Currently translated at 100.0% (12 of 12 strings) Translated using Weblate (Spanish) Currently translated at 10.8% (4 of 37 strings) Translated using Weblate (Spanish) Currently translated at 100.0% (39 of 39 strings) Translated using Weblate (Spanish) Currently translated at 5.0% (2 of 40 strings) Translated using Weblate (Spanish) Currently translated at 5.7% (2 of 35 strings) Translated using Weblate (Spanish) Currently translated at 3.5% (1 of 28 strings) Translated using Weblate (Spanish) Currently translated at 3.7% (2 of 53 strings) Translated using Weblate (Spanish) Currently translated at 6.9% (5 of 72 strings) Translated using Weblate (Spanish) Currently translated at 100.0% (3 of 3 strings) Translated using Weblate (Spanish) Currently translated at 100.0% (43 of 43 strings) Translated using Weblate (Spanish) Currently translated at 100.0% (34 of 34 strings) Translated using Weblate (Spanish) Currently translated at 7.1% (2 of 28 strings) Translated using Weblate (Spanish) Currently translated at 3.3% (1 of 30 strings) Translated using Weblate (Spanish) Currently translated at 38.8% (14 of 36 strings) Co-authored-by: Paulo Cesar <[email protected]> Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/3d/es/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/about_data/es/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/advanced_geometry_construction/es/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/backup/es/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/creating_db/es/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/equality/es/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/geography/es/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/geography_exercises/es/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/geometries/es/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/geometries_exercises/es/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/geometry_returning/es/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/geometry_returning_exercises/es/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/introduction/es/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/joins/es/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/joins_advanced/es/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/joins_exercises/es/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/license/es/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/postgis-functions/es/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/projection_exercises/es/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/schemas/es/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/simple_sql/es/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/simple_sql_exercises/es/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/spatial_relationships_exercises/es/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/topology/es/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/upgrades/es/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/validity/es/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/welcome/es/ Translation: postgis-workshop/3d Translation: postgis-workshop/about_data Translation: postgis-workshop/advanced_geometry_construction Translation: postgis-workshop/backup Translation: postgis-workshop/creating_db Translation: postgis-workshop/equality Translation: postgis-workshop/geography Translation: postgis-workshop/geography_exercises Translation: postgis-workshop/geometries Translation: postgis-workshop/geometries_exercises Translation: postgis-workshop/geometry_returning Translation: postgis-workshop/geometry_returning_exercises Translation: postgis-workshop/introduction Translation: postgis-workshop/joins Translation: postgis-workshop/joins_advanced Translation: postgis-workshop/joins_exercises Translation: postgis-workshop/license Translation: postgis-workshop/postgis-functions Translation: postgis-workshop/projection_exercises Translation: postgis-workshop/schemas Translation: postgis-workshop/simple_sql Translation: postgis-workshop/simple_sql_exercises Translation: postgis-workshop/spatial_relationships_exercises Translation: postgis-workshop/topology Translation: postgis-workshop/upgrades Translation: postgis-workshop/validity Translation: postgis-workshop/welcome
Currently translated at 100.0% (58 of 58 strings) Translated using Weblate (Chinese (Simplified)) Currently translated at 100.0% (42 of 42 strings) Translated using Weblate (Chinese (Simplified)) Currently translated at 100.0% (42 of 42 strings) Translated using Weblate (Chinese (Simplified)) Currently translated at 100.0% (62 of 62 strings) Translated using Weblate (Chinese (Simplified)) Currently translated at 100.0% (41 of 41 strings) Translated using Weblate (Chinese (Simplified)) Currently translated at 100.0% (39 of 39 strings) Translated using Weblate (Chinese (Simplified)) Currently translated at 100.0% (34 of 34 strings) Translated using Weblate (Chinese (Simplified)) Currently translated at 100.0% (28 of 28 strings) Translated using Weblate (Chinese (Simplified)) Currently translated at 50.0% (29 of 58 strings) Translated using Weblate (Chinese (Simplified)) Currently translated at 100.0% (35 of 35 strings) Translated using Weblate (Chinese (Simplified)) Currently translated at 100.0% (30 of 30 strings) Translated using Weblate (Chinese (Simplified)) Currently translated at 73.8% (31 of 42 strings) Translated using Weblate (Chinese (Simplified)) Currently translated at 100.0% (53 of 53 strings) Translated using Weblate (Chinese (Simplified)) Currently translated at 100.0% (43 of 43 strings) Translated using Weblate (Chinese (Simplified)) Currently translated at 100.0% (34 of 34 strings) Translated using Weblate (Chinese (Simplified)) Currently translated at 100.0% (94 of 94 strings) Translated using Weblate (Chinese (Simplified)) Currently translated at 100.0% (73 of 73 strings) Translated using Weblate (Chinese (Simplified)) Currently translated at 69.0% (29 of 42 strings) Translated using Weblate (Chinese (Simplified)) Currently translated at 87.8% (36 of 41 strings) Translated using Weblate (Chinese (Simplified)) Currently translated at 100.0% (121 of 121 strings) Translated using Weblate (Chinese (Simplified)) Currently translated at 71.7% (28 of 39 strings) Translated using Weblate (Chinese (Simplified)) Currently translated at 82.3% (28 of 34 strings) Translated using Weblate (Chinese (Simplified)) Currently translated at 100.0% (21 of 21 strings) Translated using Weblate (Chinese (Simplified)) Currently translated at 36.2% (21 of 58 strings) Translated using Weblate (Chinese (Simplified)) Currently translated at 59.5% (25 of 42 strings) Translated using Weblate (Chinese (Simplified)) Currently translated at 100.0% (12 of 12 strings) Translated using Weblate (Chinese (Simplified)) Currently translated at 54.7% (23 of 42 strings) Translated using Weblate (Chinese (Simplified)) Currently translated at 82.9% (34 of 41 strings) Translated using Weblate (Chinese (Simplified)) Currently translated at 58.9% (23 of 39 strings) Translated using Weblate (Chinese (Simplified)) Currently translated at 67.6% (23 of 34 strings) Translated using Weblate (Chinese (Simplified)) Currently translated at 100.0% (21 of 21 strings) Translated using Weblate (Chinese (Simplified)) Currently translated at 6.8% (4 of 58 strings) Translated using Weblate (Chinese (Simplified)) Currently translated at 14.2% (6 of 42 strings) Translated using Weblate (Chinese (Simplified)) Currently translated at 41.6% (5 of 12 strings) Translated using Weblate (Chinese (Simplified)) Currently translated at 14.2% (6 of 42 strings) Translated using Weblate (Chinese (Simplified)) Currently translated at 100.0% (3 of 3 strings) Translated using Weblate (Chinese (Simplified)) Currently translated at 30.7% (12 of 39 strings) Translated using Weblate (Chinese (Simplified)) Currently translated at 14.7% (5 of 34 strings) Translated using Weblate (Chinese (Simplified)) Currently translated at 28.5% (6 of 21 strings) Translated using Weblate (Chinese (Simplified)) Currently translated at 100.0% (29 of 29 strings) Co-authored-by: Wangdapeng <[email protected]> Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/3d/zh_Hans/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/about_data/zh_Hans/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/advanced_geometry_construction/zh_Hans/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/clusterindex/zh_Hans/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/equality/zh_Hans/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/geography_exercises/zh_Hans/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/geometries_exercises/zh_Hans/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/history_tracking/zh_Hans/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/index/zh_Hans/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/indexing/zh_Hans/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/introduction/zh_Hans/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/joins/zh_Hans/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/license/zh_Hans/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/loading_data/zh_Hans/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/postgis-functions/zh_Hans/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/projection_exercises/zh_Hans/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/simple_sql/zh_Hans/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/simple_sql_exercises/zh_Hans/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/spatial_relationships/zh_Hans/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/spatial_relationships_exercises/zh_Hans/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/upgrades/zh_Hans/ Translation: postgis-workshop/3d Translation: postgis-workshop/about_data Translation: postgis-workshop/advanced_geometry_construction Translation: postgis-workshop/clusterindex Translation: postgis-workshop/equality Translation: postgis-workshop/geography_exercises Translation: postgis-workshop/geometries_exercises Translation: postgis-workshop/history_tracking Translation: postgis-workshop/index Translation: postgis-workshop/indexing Translation: postgis-workshop/introduction Translation: postgis-workshop/joins Translation: postgis-workshop/license Translation: postgis-workshop/loading_data Translation: postgis-workshop/postgis-functions Translation: postgis-workshop/projection_exercises Translation: postgis-workshop/simple_sql Translation: postgis-workshop/simple_sql_exercises Translation: postgis-workshop/spatial_relationships Translation: postgis-workshop/spatial_relationships_exercises Translation: postgis-workshop/upgrades
osgeoweblate
force-pushed
the
weblate-postgis-workshop-index
branch
from
bd41a6d to
8a00201
Compare
There was a problem hiding this comment.
Actionable comments posted: 0
♻️ Duplicate comments (4)
postgis-intro/sources/locale/es/LC_MESSAGES/3d.po (1)
28-28:⚠️ Potential issueMissing type in Spanish translation
The English original mentions three types: "PointZ, PointM and PointZM", but the translation only includes "PointM y PointZM". This omission could cause confusion for Spanish-speaking readers.
-Point (un tipo 2-D ) es complementada por los tipos PointM y PointZM . +Point (un tipo 2-D) es complementada por los tipos PointZ, PointM y PointZM.postgis-intro/sources/locale/es/LC_MESSAGES/joins_exercises.po (3)
53-53:⚠️ Potential issueFunction name should not be translated
The function name
ST_Areahas been translated in the Spanish version, but PostGIS function names should remain unchanged while only translating parameters and descriptions. This ensures consistency with official documentation and avoids confusion.-:command:`ST_Area(geometría)` devuelve el área de la geometría. +:command:`ST_Area(geometry)` devuelve el área de la geometría.
74-75:⚠️ Potential issueFunction name should not be translated
The function name
ST_Distancehas been translated toST_Distancia. PostGIS function names should remain in English in all translations.-:command:`ST_Distancia(geometría A, geometría B)` devuelve la distancia mínima entre la geometría A y la geometría B +:command:`ST_Distance(geometría A, geometría B)` devuelve la distancia mínima entre la geometría A y la geometría B
66-67:⚠️ Potential issueFunction name should not be translated
The function name
ST_Containshas been translated toST_Contiene. PostGIS function names should remain in English in all translations to maintain consistency with the API and documentation.-:command:`ST_Contiene(geometría A, geometría B)` devuelve verdadero si la geometría A contiene a la geometría B +:command:`ST_Contains(geometría A, geometría B)` devuelve verdadero si la geometría A contiene a la geometría B
🧹 Nitpick comments (2)
postgis-intro/sources/locale/es/LC_MESSAGES/welcome.po (1)
70-70: Minor inconsistency in terminology.The translation for "bold font" keeps the English word "bold" instead of using the Spanish term "negrita" that was correctly used in line 29.
-msgstr "Cuando se definan nombres de funciones en el texto, se mostrarán en :command:`bold`." +msgstr "Cuando se definan nombres de funciones en el texto, se mostrarán en :command:`negrita`."postgis-intro/sources/locale/es/LC_MESSAGES/joins_exercises.po (1)
40-41: Consider consistency in function namingWhile translation of SQL keywords is appropriate, consider whether translating
sumtosumais consistent with how other SQL functions are handled in the documentation. If other SQL functions remain in English, consistency might favor keeping this assum(expresión).
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (48)
postgis-intro/sources/locale/es/LC_MESSAGES/3d.po(1 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/about_data.po(1 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/advanced_geometry_construction.po(7 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/backup.po(1 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/creating_db.po(5 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/equality.po(7 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/geography.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/geography_exercises.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/geometries.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/geometries_exercises.po(7 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/geometry_returning.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/geometry_returning_exercises.po(4 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/introduction.po(1 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/joins.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/joins_advanced.po(1 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/joins_exercises.po(4 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/license.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/postgis-functions.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/projection_exercises.po(6 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/schemas.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/simple_sql.po(7 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/simple_sql_exercises.po(8 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/spatial_relationships_exercises.po(5 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/topology.po(2 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/upgrades.po(3 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/validity.po(4 hunks)postgis-intro/sources/locale/es/LC_MESSAGES/welcome.po(1 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/3d.po(4 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/about_data.po(2 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/advanced_geometry_construction.po(1 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/clusterindex.po(8 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/equality.po(1 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/geography_exercises.po(2 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/geometries_exercises.po(2 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/history_tracking.po(8 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/index.po(2 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/indexing.po(3 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/introduction.po(2 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/joins.po(3 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/license.po(2 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/loading_data.po(2 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/postgis-functions.po(10 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/projection_exercises.po(2 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/simple_sql.po(2 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/simple_sql_exercises.po(3 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/spatial_relationships.po(3 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/spatial_relationships_exercises.po(2 hunks)postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/upgrades.po(7 hunks)
🚧 Files skipped from review as they are similar to previous changes (40)
- postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/geometries_exercises.po
- postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/joins.po
- postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/introduction.po
- postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/3d.po
- postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/spatial_relationships.po
- postgis-intro/sources/locale/es/LC_MESSAGES/simple_sql.po
- postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/spatial_relationships_exercises.po
- postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/simple_sql_exercises.po
- postgis-intro/sources/locale/es/LC_MESSAGES/validity.po
- postgis-intro/sources/locale/es/LC_MESSAGES/geometries.po
- postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/index.po
- postgis-intro/sources/locale/es/LC_MESSAGES/joins.po
- postgis-intro/sources/locale/es/LC_MESSAGES/equality.po
- postgis-intro/sources/locale/es/LC_MESSAGES/geography.po
- postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/history_tracking.po
- postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/geography_exercises.po
- postgis-intro/sources/locale/es/LC_MESSAGES/about_data.po
- postgis-intro/sources/locale/es/LC_MESSAGES/geometry_returning.po
- postgis-intro/sources/locale/es/LC_MESSAGES/topology.po
- postgis-intro/sources/locale/es/LC_MESSAGES/creating_db.po
- postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/license.po
- postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/about_data.po
- postgis-intro/sources/locale/es/LC_MESSAGES/license.po
- postgis-intro/sources/locale/es/LC_MESSAGES/introduction.po
- postgis-intro/sources/locale/es/LC_MESSAGES/spatial_relationships_exercises.po
- postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/simple_sql.po
- postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/loading_data.po
- postgis-intro/sources/locale/es/LC_MESSAGES/schemas.po
- postgis-intro/sources/locale/es/LC_MESSAGES/projection_exercises.po
- postgis-intro/sources/locale/es/LC_MESSAGES/joins_advanced.po
- postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/equality.po
- postgis-intro/sources/locale/es/LC_MESSAGES/geometries_exercises.po
- postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/projection_exercises.po
- postgis-intro/sources/locale/es/LC_MESSAGES/postgis-functions.po
- postgis-intro/sources/locale/es/LC_MESSAGES/upgrades.po
- postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/postgis-functions.po
- postgis-intro/sources/locale/es/LC_MESSAGES/geometry_returning_exercises.po
- postgis-intro/sources/locale/es/LC_MESSAGES/backup.po
- postgis-intro/sources/locale/es/LC_MESSAGES/geography_exercises.po
- postgis-intro/sources/locale/es/LC_MESSAGES/simple_sql_exercises.po
🔇 Additional comments (21)
postgis-intro/sources/locale/es/LC_MESSAGES/welcome.po (3)
7-7: Good addition of new translator credit.The addition of Paulo Cesar as a translator with the 2025 date correctly attributes the new translation work.
9-9: Metadata properly updated for the new translation revision.The PO-Revision-Date has been updated to 2025-03-27, and all other metadata fields are correctly set for Spanish localization, including plural forms and language team URL.
17-106: High-quality Spanish translations added.The translations accurately convey the meaning of the original English text while maintaining a natural flow in Spanish. Technical terms are preserved appropriately, and formatting markers for UI elements (bold, fixed-width, italics) are correctly handled in the translations.
postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/clusterindex.po (2)
5-5: Metadata updates look goodThe translator information, revision date, and Weblate generator version have been properly updated. The file now correctly attributes Wangdapeng as the translator with the appropriate email and updated revision date of March 27, 2025.
Also applies to: 11-12, 20-20
24-24: Complete Chinese translation additions look excellentThe previously empty msgstr fields have been filled with high-quality Chinese translations that accurately convey the technical content about database clustering, spatial indexes, and performance considerations. Technical terms are properly handled, with Chinese translations accompanied by English originals in parentheses where appropriate (e.g., "聚类"（Clustering）).
The translations maintain the original meaning while being natural in Chinese, properly explaining complex concepts like memory hierarchy, spatial correlation, and database performance considerations.
Also applies to: 33-35, 42-43, 50-51, 58-59, 65-65, 69-69, 76-77, 84-85, 89-89, 98-100, 104-104, 114-116, 120-120, 129-130, 142-145, 149-149, 156-157, 166-167, 178-179
postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/advanced_geometry_construction.po (2)
4-4: Metadata properly updated with current translation informationThe translation file metadata has been correctly updated with:
- Current translator information with updated year (2025)
- Current revision date (April 1, 2025)
- Proper language team URL for the Chinese (Simplified) translation project
- Appropriate plural forms specification for Chinese
- Generator information showing Weblate 5.4.3 was used
These updates follow standard PO file conventions and provide proper attribution and technical metadata.
Also applies to: 10-13, 18-19
23-23: Translation content consistently preserves formatting and technical elementsThe Chinese translations have been added throughout the document while properly maintaining:
- Code formatting with backticks (e.g.,
nyc_subway_stations,routes)- Technical function names and SQL syntax
- Hyperlink structures
- Paragraph formatting and sentence structure
The translations appear complete and maintain the technical integrity of the original document while making it accessible to Chinese readers.
Also applies to: 27-28, 33-34, 38-38, 43-44, 48-49, 53-54, 58-58, 61-62, 66-67, 71-71, 76-77, 82-83, 88-89, 93-93, 97-98, 103-107, 111-111, 116-117, 121-121, 126-128, 133-135, 139-139, 143-143, 147-147, 150-151, 155-156, 160-161, 165-165, 169-170, 174-175, 179-180, 185-186, 190-190, 194-194, 199-202, 206-207, 211-211, 215-216, 220-221, 225-225, 229-230, 234-234, 239-240, 245-247, 251-252, 256-256, 260-260, 264-264, 268-268, 273-274, 278-279, 283-284, 288-288, 293-294, 299-300, 305-306, 310-310
postgis-intro/sources/locale/es/LC_MESSAGES/advanced_geometry_construction.po (6)
6-7: Metadata update looks good.The translator information, revision date, and generator version have been properly updated. This ensures correct attribution and versioning information.
Also applies to: 13-14, 22-22
26-27: Great addition of missing translation.The title "Advanced Geometry Constructions" has been translated as "Construcción de Geometrías" which is appropriate and concise.
33-35: Excellent translation of technical content.The translations accurately preserve technical terms like "nyc_subway_stations", "PostgreSQL", and "PostGIS" while providing clear Spanish explanations of the concepts. The formatting and code references are also properly maintained.
Also applies to: 44-47, 51-51, 59-61, 70-74, 81-82, 86-86, 93-93
101-104: Technical terminology translation is well-executed.The translations correctly handle technical terminology related to database concepts (CTE, PL/PgSQL, recursive expressions). The explanations maintain technical accuracy while being natural in Spanish.
Also applies to: 109-110, 117-118, 125-126, 134-137, 141-141, 149-151, 162-167, 174-175
183-185: Good consistency in ARRAY operations translation.The PostgreSQL array operations and technical explanations are consistently translated, maintaining the correct syntax for code elements like
array_append, @>, and proper formatting for code blocks.Also applies to: 191-192, 201-205, 215-220, 224-224, 228-228, 232-232, 239-240, 248-250, 257-259, 266-267, 275-277, 286-289, 296-297, 305-307
310-453: Missing translations for the latter part of the document.There are no translations provided for content starting from line 314 through the end of the file. This includes explanations about route finding, array functions, and various technical sections. Consider completing these translations in a future update.
Are these translations intentionally omitted from this PR, or should they be included to complete the Spanish localization of this document?
postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/upgrades.po (4)
5-5: Well-structured metadata updates for the Chinese translation.The translator information, revision date, language team, and plural forms have been properly configured according to standard PO file conventions. This ensures proper attribution and configuration for the Chinese translation.
Also applies to: 11-14, 19-20
24-24: Excellent translation of section titles.All section headings have been accurately translated to Simplified Chinese while preserving their technical meaning. The translations are concise and appropriate for a technical document.
Also applies to: 51-51, 55-55, 59-59, 83-83, 93-93, 101-101, 147-147, 208-208
33-35: Clear and technically accurate translations for upgrade procedures.The translations of the technical content properly maintain:
- The technical meaning of database concepts and operations
- Correct formatting for code elements (using backticks)
- Appropriate Chinese terminology for PostgreSQL and PostGIS operations
The explanations of upgrade processes are well-translated and would be clear to Chinese-speaking database administrators.
Also applies to: 45-47, 68-70, 78-79, 89-89, 97-97, 112-115, 119-119, 128-129, 135-135, 139-139, 143-143, 156-158, 164-164, 171-171, 175-175, 181-181, 186-186, 190-190, 196-196, 200-200, 204-204, 216-217, 221-221, 225-225
11-11: Note the future-dated revision timestamp.The PO-Revision-Date is set to 2025-04-01, which is in the future. While this doesn't affect functionality, you might want to verify if this is intentional or needs correction.
postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/indexing.po (3)
278-279: Improved translation clarityThe translation has been refined to be more concise and clearer in Chinese, making it easier for readers to understand how to add index acceleration to functions not in the list.
454-456: Clarified geometry equality behaviorThe updated translation now correctly specifies the version-specific behavior of the equality operator, noting that only in PostGIS 2.4+ does it require complete geometry equality rather than just bounding box equality.
463-464: Enhanced translation accuracyThe translation for the
~=operator has been improved, making it clearer that it's specifically checking bounding box equality.postgis-intro/sources/locale/es/LC_MESSAGES/joins_exercises.po (1)
82-83:⚠️ Potential issueKeep function name in English
Similar to other PostGIS functions,
ST_DWithinshould remain in English and not be translated, while parameters can be translated.-:command:`ST_DWithin(geometría A, geometría B, radio)` devuelve verdadero si la geometría A está a una distancia dentro del 'radio' de la geometría B +:command:`ST_DWithin(geometría A, geometría B, radio)` devuelve verdadero si la geometría A está a una distancia dentro del 'radio' de la geometría BLikely an incorrect or invalid review comment.
Translations update from OSGeo Weblate for postgis-workshop/index.
It also includes following components:
postgis-workshop/spatial_relationships_exercises
postgis-workshop/geography_exercises
postgis-workshop/joins_exercises
postgis-workshop/projection_exercises
postgis-workshop/advanced_geometry_construction
postgis-workshop/simple_sql_exercises
postgis-workshop/3d
postgis-workshop/backup
postgis-workshop/license
postgis-workshop/installation
postgis-workshop/knn
postgis-workshop/equality
postgis-workshop/joins_advanced
postgis-workshop/welcome
postgis-workshop/topology
postgis-workshop/tuning
postgis-workshop/security
postgis-workshop/upgrades
postgis-workshop/clusterindex
postgis-workshop/introduction
postgis-workshop/linear_referencing
postgis-workshop/loading_data
postgis-workshop/about_data
postgis-workshop/rasters
postgis-workshop/history_tracking
postgis-workshop/de9im
postgis-workshop/geometries
postgis-workshop/glossary 1
postgis-workshop/validity
postgis-workshop/simple_sql
postgis-workshop/geometries_exercises
postgis-workshop/geometry_returning
postgis-workshop/schemas
postgis-workshop/creating_db
postgis-workshop/postgis-functions
postgis-workshop/joins
postgis-workshop/projection
postgis-workshop/spatial_relationships
postgis-workshop/geometry_returning_exercises
postgis-workshop/indexing
postgis-workshop/geography
Current translation status: