Translations update from OSGeo Weblate #141
Conversation
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/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_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/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/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/ Translation: postgis-workshop/3d Translation: postgis-workshop/about_data Translation: postgis-workshop/backup Translation: postgis-workshop/creating_db Translation: postgis-workshop/equality 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/joins Translation: postgis-workshop/joins_advanced Translation: postgis-workshop/joins_exercises Translation: postgis-workshop/license 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
📝 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
Tip ⚡🧪 Multi-step agentic review comment chat (experimental)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 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.
| "todos y cada uno de los vértices de la geometría para determinar la " | ||
| "igualdad. Esto puede ser lento, y puede no ser apropiado para comparar un " | ||
| "gran número de geometrías. Para permitir una comparación más rápida, se " | ||
| "proporciona el operador de límites iguales, :comando:`~=`. Este operador " |
There was a problem hiding this comment.
Fix 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 "📝 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.
| "proporciona el operador de límites iguales, :comando:`~=`. Este operador " | |
| "proporciona el operador de límites iguales, :command:`~=`. Este operador " |
|
|
||
| #: ../../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.
|
|
||
| #: ../../en/simple_sql_exercises.rst:118 | ||
| msgid "**For each borough, what percentage of the population is white?**" | ||
| msgstr "" | ||
| msgstr "**¿Qué porcentaje de población negra hay en cada distrito?" |
There was a problem hiding this comment.
Fix 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?"📝 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 "**¿Qué porcentaje de población negra hay en cada distrito?" | |
| msgstr "**¿Qué porcentaje de población blanca hay en cada distrito?" |
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: