Translations update from OSGeo Weblate #154
Conversation
📝 WalkthroughWalkthroughAdded a broad set of Ukrainian gettext catalogs for the "Introduction to PostGIS" workshop and expanded translations and metadata in the existing Ukrainian Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~15 minutes Possibly related PRs
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
✨ Finishing Touches🧪 Generate unit tests
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:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR/Issue comments)Type 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: 2
🧹 Nitpick comments (2)
postgis-intro/sources/locale/uk/LC_MESSAGES/validity.po (2)
18-153: Untranslated entries: confirm intent (empty msgstr for all msgids)All msgstr values are empty. If this is an initial skeleton from Weblate, fine; otherwise consider committing only translated strings or mark as WIP.
Confirm if this file is intentionally an untranslated stub. I can help script a check for non-empty translations or batch import suggestions from Weblate.
111-111: Prefer HTTPS for docs/tool links (upstream content)Links use http://; switch to https:// in the English source where supported:
- postgis.net/docs/ST_MakeValid.html
- openjump.org
I can submit a small upstream docs PR to flip these to HTTPS and refresh the catalog.
Also applies to: 119-119, 135-135, 151-151
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
postgis-intro/sources/locale/uk/LC_MESSAGES/validity.po(1 hunks)
🔇 Additional comments (1)
postgis-intro/sources/locale/uk/LC_MESSAGES/validity.po (1)
1-4: LGTM: file placement and metadata blockNew uk locale file is correctly placed under locale/uk/LC_MESSAGES with standard header preamble and translator credit. Good.
| msgstr "" | ||
|
|
||
| #: ../../en/validity.rst:165 | ||
| msgid "`ST_IsValid(geometry A) <http://postgis.net/docs/ST_IsValid.html>`_: Returns a boolean indiciting whether the geometery is valid." |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Upstream typos in English source (msgid): “indiciting”, “geometery”
These are in msgid and should be fixed upstream in the English source, not in this PO.
Propose to change to: “indicating” and “geometry” in the English .rst, then regenerate POT/PO. I can open an upstream fix if desired.
🤖 Prompt for AI Agents
In postgis-intro/sources/locale/uk/LC_MESSAGES/validity.po at line 143, the
English source msgid contains typos "indiciting" and "geometery". These should
be corrected upstream in the original English .rst documentation file by
changing them to "indicating" and "geometry". After fixing the .rst file,
regenerate the POT and PO files to propagate the corrections properly instead of
editing the translation file directly.
osgeoweblate
force-pushed
the
weblate-postgis-workshop-index
branch
12 times, most recently
from
34c3a85 to
1f8a505
Compare
There was a problem hiding this comment.
Actionable comments posted: 2
🔭 Outside diff range comments (1)
postgis-intro/sources/locale/uk/LC_MESSAGES/equality.po (1)
1-107: Unify terminology for “polygon” in Ukrainian translationsWe’ve spotted mixed use of “багатокутник/багатокутники” and “полігон/полігони” in several UA PO files. Please choose one term (e.g. «полігон») and apply it consistently:
• postgis-intro/sources/locale/uk/LC_MESSAGES/equality.po
– lines 34, 38, 55–57, 60, 78–80, 101• postgis-intro/sources/locale/uk/LC_MESSAGES/introduction.po
– lines 58, 165, 183–184• postgis-intro/sources/locale/uk/LC_MESSAGES/validity.po
– lines 40, 47, 72, 95, 107, 112, 133, 164, 166, 177, 185, 191Example diff for equality.po:
- "будемо використовувати наступні полігони." + "будемо використовувати наступні полігони." - msgstr "Ці багатокутники завантажуються за допомогою наступних команд." + msgstr "Ці полігони завантажуються за допомогою наступних команд." - "У цьому прикладі багатокутники рівні тільки самі собі…" + "У цьому прикладі полігони рівні тільки самі собі…"After updating, verify compilation with:
msgfmt -c -o /dev/null postgis-intro/sources/locale/uk/LC_MESSAGES/*.po
🧹 Nitpick comments (3)
postgis-intro/sources/locale/uk/LC_MESSAGES/equality.po (3)
41-43: Normalize “Exact equality” to a noun phrase for consistency (Точна рівність)Headings elsewhere use nouns (“Рівність”), but here it’s an adjective phrase. Suggest aligning heading and references.
- msgstr "Абсолютно однакові" + msgstr "Точна рівність"- "Абсолютна однаковість визначається шляхом порівняння двох геометрій, вершина " + "Точна рівність визначається шляхом порівняння двох геометрій, вершина "- "Абсолютна однаковість вимагає, в найгіршому випадку, порівняння кожної " + "Точна рівність вимагає, в найгіршому випадку, порівняння кожної "Also applies to: 47-47, 89-89
63-65: Use a noun phrase for “Spatially Equal” and align the paragraph wordingKeeps section titles stylistically consistent and matches the term in text.
- msgstr "Просторово однакові" + msgstr "Просторова рівність"- "яка дозволяє перевірити просторову однаковість або еквівалентність геометрій." + "яка дозволяє перевірити просторову рівність або еквівалентність геометрій."Also applies to: 71-71
18-19: Nit: wrap the plural rule in parentheses (common Ukrainian PO convention)Functionally equivalent, but improves readability and follows typical UA PO headers.
- "Plural-Forms: nplurals=3; plural=n%10==1 && n%100!=11 ? 0 : n%10>=2 && " - "n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2;\n" + "Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && " + "n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (11)
postgis-intro/sources/locale/uk/LC_MESSAGES/3d.po(1 hunks)postgis-intro/sources/locale/uk/LC_MESSAGES/about_data.po(1 hunks)postgis-intro/sources/locale/uk/LC_MESSAGES/equality.po(1 hunks)postgis-intro/sources/locale/uk/LC_MESSAGES/geography_exercises.po(1 hunks)postgis-intro/sources/locale/uk/LC_MESSAGES/geometries_exercises.po(1 hunks)postgis-intro/sources/locale/uk/LC_MESSAGES/index.po(1 hunks)postgis-intro/sources/locale/uk/LC_MESSAGES/installation.po(1 hunks)postgis-intro/sources/locale/uk/LC_MESSAGES/introduction.po(1 hunks)postgis-intro/sources/locale/uk/LC_MESSAGES/knn.po(1 hunks)postgis-intro/sources/locale/uk/LC_MESSAGES/license.po(1 hunks)postgis-intro/sources/locale/uk/LC_MESSAGES/validity.po(1 hunks)
✅ Files skipped from review due to trivial changes (3)
- postgis-intro/sources/locale/uk/LC_MESSAGES/geometries_exercises.po
- postgis-intro/sources/locale/uk/LC_MESSAGES/validity.po
- postgis-intro/sources/locale/uk/LC_MESSAGES/index.po
🚧 Files skipped from review as they are similar to previous changes (7)
- postgis-intro/sources/locale/uk/LC_MESSAGES/about_data.po
- postgis-intro/sources/locale/uk/LC_MESSAGES/geography_exercises.po
- postgis-intro/sources/locale/uk/LC_MESSAGES/introduction.po
- postgis-intro/sources/locale/uk/LC_MESSAGES/knn.po
- postgis-intro/sources/locale/uk/LC_MESSAGES/installation.po
- postgis-intro/sources/locale/uk/LC_MESSAGES/license.po
- postgis-intro/sources/locale/uk/LC_MESSAGES/3d.po
🔇 Additional comments (1)
postgis-intro/sources/locale/uk/LC_MESSAGES/equality.po (1)
1-21: PO header and overall translation quality look solidHeaders are well-formed, msgstr entries are complete, and reST roles are preserved. Nice work.
| #: ../../en/equality.rst:14 | ||
| msgid "These polygons are loaded using the following commands." | ||
| msgstr "Ці багатокутники завантажуються за допомогою наступних команд." | ||
|
|
There was a problem hiding this comment.
🛠️ Refactor suggestion
Standardize terminology: use “полігон” consistently instead of mixing with “багатокутник”
GIS materials commonly use “полігон”. Unifying terms improves readability.
- msgstr "Ці багатокутники завантажуються за допомогою наступних команд."
+ msgstr "Ці полігони завантажуються за допомогою наступних команд."- "У цьому прикладі багатокутники рівні тільки самі собі, а не іншим, на перший "
+ "У цьому прикладі полігони рівні тільки самі собі, а не іншим, на перший "
- "погляд, еквівалентним багатокутникам (як у випадку багатокутників 1–3). У "
+ "погляд, еквівалентним полігонам (як у випадку полігонів 1–3). У "
- "випадку багатокутників 1, 2 і 3 вершини знаходяться в однакових положеннях, "
+ "випадку полігонів 1, 2 і 3 вершини знаходяться в однакових положеннях, "
- "але визначені в різному порядку. Багатокутник 4 має колінеарні (а отже, "
+ "але визначені в різному порядку. Полігон 4 має колінеарні (а отже, "
- "надлишкові) вершини на ребрах шестикутника, що спричиняє нерівність з "
- "багатокутником 1."
+ "надлишкові) вершини на ребрах шестикутника, що спричиняє нерівність із "
+ "полігоном 1."- "жаль, багатокутник 5 також повертається як рівний за результатами цього "
+ "жаль, полігон 5 також повертається як рівний за результатами цього "Also applies to: 55-61, 100-103
🤖 Prompt for AI Agents
In postgis-intro/sources/locale/uk/LC_MESSAGES/equality.po around lines 36 to 39
(and also check ranges 55-61 and 100-103), the translation uses “багатокутник”
while the project prefers the term “полігон”; update the msgstr values to
replace “багатокутник” with “полігон” so the terminology is consistent across
the file, and run a quick search for any remaining occurrences to standardize
them as well.
| "швидкого порівняння передбачений оператор рівних меж :command:`~=`. Він " | ||
| "працює тільки з обмежувальним прямокутником (прямокутником), гарантуючи, що " | ||
| "геометрії займають однакову двовимірну площу, але не обов'язково однаковий " | ||
| "простір." |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Fix “bounding box” translation and remove accidental duplication
Use standard “обмежувальна рамка (прямокутник)” and avoid “коробка”.
- "працює тільки з обмежувальним прямокутником (прямокутником), гарантуючи, що "
+ "працює тільки з обмежувальною рамкою (прямокутником), гарантуючи, що "- "тесту, оскільки він має ту саму обмежувальну коробку, що й інші геометрії. "
+ "тесту, оскільки він має ту саму обмежувальну рамку, що й інші геометрії. "Also applies to: 101-102
🤖 Prompt for AI Agents
In postgis-intro/sources/locale/uk/LC_MESSAGES/equality.po around lines 92-95
(and also apply the same change to lines 101-102), the phrase incorrectly uses
"обмежувальним прямокутником (прямокутником)" and the word "коробка" — update
the translation to use the standard term "обмежувальна рамка (прямокутник)"
(remove the duplicated "прямокутником" and any use of "коробка") so the sentence
reads with the corrected phrase and no duplication in both places mentioned.
1f8a505 to
3814dc2
Compare
Currently translated at 55.1% (16 of 29 strings) Translated using Weblate (Ukrainian) Currently translated at 100.0% (53 of 53 strings) Translated using Weblate (Ukrainian) Currently translated at 100.0% (39 of 39 strings) Translated using Weblate (Ukrainian) Currently translated at 100.0% (21 of 21 strings) Added translation using Weblate (Ukrainian) Added translation using Weblate (Ukrainian) Translated using Weblate (Ukrainian) Currently translated at 94.8% (37 of 39 strings) Translated using Weblate (Ukrainian) Currently translated at 100.0% (15 of 15 strings) Translated using Weblate (Ukrainian) Currently translated at 100.0% (3 of 3 strings) Translated using Weblate (Ukrainian) Currently translated at 100.0% (12 of 12 strings) Added translation using Weblate (Ukrainian) Added translation using Weblate (Ukrainian) Added translation using Weblate (Ukrainian) Added translation using Weblate (Ukrainian) Translated using Weblate (Ukrainian) Currently translated at 100.0% (94 of 94 strings) Translated using Weblate (Ukrainian) Currently translated at 100.0% (21 of 21 strings) Translated using Weblate (Ukrainian) Currently translated at 100.0% (25 of 25 strings) Added translation using Weblate (Ukrainian) Added translation using Weblate (Ukrainian) Translated using Weblate (Ukrainian) Currently translated at 100.0% (29 of 29 strings) Translated using Weblate (Ukrainian) Currently translated at 100.0% (34 of 34 strings) Translated using Weblate (Ukrainian) Currently translated at 100.0% (121 of 121 strings) Added translation using Weblate (Ukrainian) Added translation using Weblate (Ukrainian) Added translation using Weblate (Ukrainian) Co-authored-by: Denys Kovshun <[email protected]> Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/3d/uk/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/about_data/uk/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/equality/uk/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/geography_exercises/uk/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/geometries_exercises/uk/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/index/uk/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/installation/uk/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/introduction/uk/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/joins_exercises/uk/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/knn/uk/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/license/uk/ Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/validity/uk/ Translation: postgis-workshop/3d Translation: postgis-workshop/about_data Translation: postgis-workshop/equality Translation: postgis-workshop/geography_exercises Translation: postgis-workshop/geometries_exercises Translation: postgis-workshop/index Translation: postgis-workshop/installation Translation: postgis-workshop/introduction Translation: postgis-workshop/joins_exercises Translation: postgis-workshop/knn Translation: postgis-workshop/license Translation: postgis-workshop/validity
Currently translated at 55.1% (16 of 29 strings) Co-authored-by: Weblate Translation Memory <[email protected]> Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/joins_exercises/uk/ Translation: postgis-workshop/joins_exercises
Currently translated at 55.1% (16 of 29 strings) Co-authored-by: Weblate <[email protected]> Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/joins_exercises/uk/ Translation: postgis-workshop/joins_exercises
osgeoweblate
force-pushed
the
weblate-postgis-workshop-index
branch
from
3814dc2 to
be99817
Compare
Currently translated at 96.5% (28 of 29 strings) Translation: postgis-workshop/joins_exercises Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/joins_exercises/uk/
Currently translated at 96.5% (28 of 29 strings) Translation: postgis-workshop/joins_exercises Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/joins_exercises/uk/
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (4)
postgis-intro/sources/locale/uk/LC_MESSAGES/geometries_exercises.po (2)
36-37: Minor formatting inconsistency in command references.Several msgstr entries are missing spaces after the closing backtick in
:command:references, which creates inconsistent formatting compared to other entries.For example, on lines 36-37:
-":command:`sum(expression)`агрегатна функція, що повертає суму для набору " +":command:`sum(expression)` агрегатна функція, що повертає суму для набору "Similar formatting should be applied to other command references for consistency.
Also applies to: 41-42, 55-57, 72-74
166-166: Minor typo in Ukrainian translation.There's a small typo in the translation.
-msgstr ":command:`ST_AsGeoJSON(geometry)` повретає JSON ``text``" +msgstr ":command:`ST_AsGeoJSON(geometry)` повертає JSON ``text``"postgis-intro/sources/locale/uk/LC_MESSAGES/joins_exercises.po (2)
40-41: Formatting consistency issue with command references.Same formatting inconsistency as in geometries_exercises.po - missing spaces after command references.
Apply consistent spacing after
:command:references:-":command:`sum(expression)`агрегатна функція, що повертає суму для набору " +":command:`sum(expression)` агрегатна функція, що повертає суму для набору "Also applies to: 48-49, 72-73
188-189: Incomplete translation for final exercise.The last exercise question remains untranslated.
The msgstr for "What neighborhood has the highest population density (persons/km2)?" is empty. Would you like me to suggest a Ukrainian translation or should this be completed by the translation team?
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (14)
postgis-intro/sources/locale/uk/LC_MESSAGES/3d.po(1 hunks)postgis-intro/sources/locale/uk/LC_MESSAGES/about_data.po(1 hunks)postgis-intro/sources/locale/uk/LC_MESSAGES/clusterindex.po(1 hunks)postgis-intro/sources/locale/uk/LC_MESSAGES/equality.po(1 hunks)postgis-intro/sources/locale/uk/LC_MESSAGES/geography_exercises.po(1 hunks)postgis-intro/sources/locale/uk/LC_MESSAGES/geometries_exercises.po(1 hunks)postgis-intro/sources/locale/uk/LC_MESSAGES/index.po(1 hunks)postgis-intro/sources/locale/uk/LC_MESSAGES/installation.po(1 hunks)postgis-intro/sources/locale/uk/LC_MESSAGES/introduction.po(1 hunks)postgis-intro/sources/locale/uk/LC_MESSAGES/joins_exercises.po(1 hunks)postgis-intro/sources/locale/uk/LC_MESSAGES/knn.po(1 hunks)postgis-intro/sources/locale/uk/LC_MESSAGES/license.po(1 hunks)postgis-intro/sources/locale/uk/LC_MESSAGES/projection.po(1 hunks)postgis-intro/sources/locale/uk/LC_MESSAGES/validity.po(1 hunks)
✅ Files skipped from review due to trivial changes (1)
- postgis-intro/sources/locale/uk/LC_MESSAGES/knn.po
🚧 Files skipped from review as they are similar to previous changes (8)
- postgis-intro/sources/locale/uk/LC_MESSAGES/geography_exercises.po
- postgis-intro/sources/locale/uk/LC_MESSAGES/installation.po
- postgis-intro/sources/locale/uk/LC_MESSAGES/about_data.po
- postgis-intro/sources/locale/uk/LC_MESSAGES/validity.po
- postgis-intro/sources/locale/uk/LC_MESSAGES/equality.po
- postgis-intro/sources/locale/uk/LC_MESSAGES/index.po
- postgis-intro/sources/locale/uk/LC_MESSAGES/3d.po
- postgis-intro/sources/locale/uk/LC_MESSAGES/license.po
🔇 Additional comments (6)
postgis-intro/sources/locale/uk/LC_MESSAGES/clusterindex.po (1)
1-101: LGTM: Proper PO file structure with template ready for translation.The file follows standard gettext PO format with correct headers and metadata. All msgstr entries are appropriately empty, indicating this is a translation template ready for Ukrainian translations to be added.
postgis-intro/sources/locale/uk/LC_MESSAGES/projection.po (1)
1-141: LGTM: Well-structured translation template for projection documentation.The file maintains proper PO format with complete English source strings ready for Ukrainian translation. The content covers essential PostGIS projection concepts including coordinate transformations and SRID management.
postgis-intro/sources/locale/uk/LC_MESSAGES/geometries_exercises.po (1)
23-264: LGTM: Comprehensive and high-quality Ukrainian translations.The translations are thorough and technically accurate, covering all PostGIS geometry functions and exercise content. The Ukrainian text properly conveys the technical concepts while maintaining readability.
postgis-intro/sources/locale/uk/LC_MESSAGES/joins_exercises.po (1)
24-187: LGTM: Well-executed translations for spatial joins content.The Ukrainian translations accurately convey the spatial joins concepts and exercise instructions, maintaining technical precision while being accessible to Ukrainian speakers.
postgis-intro/sources/locale/uk/LC_MESSAGES/introduction.po (2)
4-4: LGTM: Properly updated metadata for expanded translations.The header metadata has been correctly updated with current translator information, revision dates, and Weblate integration details including proper Ukrainian plural forms.
Also applies to: 10-20
24-720: Excellent comprehensive Ukrainian translations for core PostGIS concepts.The translations demonstrate high technical accuracy and linguistic quality, effectively conveying complex spatial database concepts, PostgreSQL features, PostGIS history, and application ecosystem information to Ukrainian speakers. The work significantly enhances accessibility of PostGIS documentation for the Ukrainian GIS community.
Currently translated at 100.0% (39 of 39 strings) Translation: postgis-workshop/3d Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/3d/uk/
Currently translated at 100.0% (29 of 29 strings) Translation: postgis-workshop/joins_exercises Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/joins_exercises/uk/
Currently translated at 100.0% (21 of 21 strings) Translation: postgis-workshop/clusterindex Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/clusterindex/uk/
Currently translated at 16.1% (5 of 31 strings) Translation: postgis-workshop/projection Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/projection/uk/
Currently translated at 100.0% (31 of 31 strings) Translation: postgis-workshop/projection Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/projection/uk/
Currently translated at 32.5% (14 of 43 strings) Translation: postgis-workshop/simple_sql_exercises Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/simple_sql_exercises/uk/
Currently translated at 32.5% (14 of 43 strings) Translation: postgis-workshop/simple_sql_exercises Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/simple_sql_exercises/uk/
Currently translated at 32.5% (14 of 43 strings) Translation: postgis-workshop/simple_sql_exercises Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/simple_sql_exercises/uk/
There was a problem hiding this comment.
Actionable comments posted: 8
🔭 Outside diff range comments (1)
postgis-intro/sources/locale/uk/LC_MESSAGES/simple_sql_exercises.po (1)
189-204: Translate “Function List” section and preserve linksKeep the RST link markup intact while localizing the descriptions.
msgid "Function List" -msgstr "" +msgstr "Список функцій" @@ msgid "`avg(expression) <http://www.postgresql.org/docs/current/static/functions-aggregate.html#FUNCTIONS-AGGREGATE-TABLE>`_: PostgreSQL aggregate function that returns the average value of a numeric column." -msgstr "" +msgstr "`avg(expression) <http://www.postgresql.org/docs/current/static/functions-aggregate.html#FUNCTIONS-AGGREGATE-TABLE>`_: Агрегатна функція PostgreSQL, що повертає середнє значення числового стовпця." @@ msgid "`count(expression) <http://www.postgresql.org/docs/current/static/functions-aggregate.html#FUNCTIONS-AGGREGATE-TABLE>`_: PostgreSQL aggregate function that returns the number of records in a set of records." -msgstr "" +msgstr "`count(expression) <http://www.postgresql.org/docs/current/static/functions-aggregate.html#FUNCTIONS-AGGREGATE-TABLE>`_: Агрегатна функція PostgreSQL, що повертає кількість записів у наборі." @@ msgid "`sum(expression) <http://www.postgresql.org/docs/current/static/functions-aggregate.html#FUNCTIONS-AGGREGATE-TABLE>`_: PostgreSQL aggregate function that returns the sum of records in a set of records." -msgstr "" +msgstr "`sum(expression) <http://www.postgresql.org/docs/current/static/functions-aggregate.html#FUNCTIONS-AGGREGATE-TABLE>`_: Агрегатна функція PostgreSQL, що повертає суму значень у наборі записів."
🧹 Nitpick comments (3)
postgis-intro/sources/locale/uk/LC_MESSAGES/simple_sql_exercises.po (3)
12-15: Set Last-Translator to the human contributor (not the bot)Align the header with the named translator listed in the comments.
-"Last-Translator: Weblate <[email protected]>\n" +"Last-Translator: Denys Kovshun <[email protected]>\n"
45-49: Minor style nit: example formattingOptional: wrap the example code in backticks to match RST style.
-"15-значний код, який однозначно ідентифікує кожен **блок** перепису. " -"Наприклад: 360050001009000" +"15-значний код, який однозначно ідентифікує кожен **блок** перепису. " +"Наприклад: ``360050001009000``"
165-168: Typography: use straight ASCII quotes in source-like strings when appropriateIf the build system enforces ASCII in code contexts, consider replacing «B» with plain 'B'. If not enforced, you can ignore.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
postgis-intro/sources/locale/uk/LC_MESSAGES/projection.po(1 hunks)postgis-intro/sources/locale/uk/LC_MESSAGES/simple_sql_exercises.po(1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
- postgis-intro/sources/locale/uk/LC_MESSAGES/projection.po
🔇 Additional comments (1)
postgis-intro/sources/locale/uk/LC_MESSAGES/simple_sql_exercises.po (1)
20-21: Plural-Forms header looks correct for UkrainianThe plural rule matches standard UA pluralization (3 forms). No change needed.
| #: ../../en/simple_sql_exercises.rst:6 | ||
| msgid "Using the ``nyc_census_blocks`` table, answer the following questions (don't peek at the answers!)." | ||
| msgstr "" | ||
| "Використовуючи таблицю «nyc_census_blocks», дайте відповіді на наступні " | ||
| "питання (не підглядайте відповіді!)." | ||
|
|
There was a problem hiding this comment.
Preserve RST inline code markup around table name
Use double backticks for code literals, not guillemets, to avoid formatting issues in Sphinx.
-"Використовуючи таблицю «nyc_census_blocks», дайте відповіді на наступні "
+"Використовуючи таблицю ``nyc_census_blocks``, дайте відповіді на наступні "
"питання (не підглядайте відповіді!)."📝 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.
| #: ../../en/simple_sql_exercises.rst:6 | |
| msgid "Using the ``nyc_census_blocks`` table, answer the following questions (don't peek at the answers!)." | |
| msgstr "" | |
| "Використовуючи таблицю «nyc_census_blocks», дайте відповіді на наступні " | |
| "питання (не підглядайте відповіді!)." | |
| #: ../../en/simple_sql_exercises.rst:6 | |
| msgid "Using the ``nyc_census_blocks`` table, answer the following questions (don't peek at the answers!)." | |
| msgstr "" | |
| "Використовуючи таблицю ``nyc_census_blocks``, дайте відповіді на наступні " | |
| "питання (не підглядайте відповіді!)." |
🤖 Prompt for AI Agents
In postgis-intro/sources/locale/uk/LC_MESSAGES/simple_sql_exercises.po around
lines 28 to 33, the localized msgstr uses guillemets (« ») around the table name
instead of RST inline code markup; replace the guillemets with double backticks
so the table name appears as an inline code literal (``nyc_census_blocks``),
preserving Sphinx formatting and escaping any existing backticks if necessary.
| msgid "Number of people self-identifying as \"white\" in the block" | ||
| msgstr "Кількість людей, які самоідентифікуються як «білі» у цьому кварталі" | ||
|
|
There was a problem hiding this comment.
🛠️ Refactor suggestion
Unify the term for “block” across translations
Current strings mix “кварталі” and “переписному блоці”. Use one consistent term; recommending “переписному блоці” to match earlier usage.
-"Кількість людей, які самоідентифікуються як «білі» у цьому кварталі"
+"Кількість людей, які самоідентифікуються як «білі» у переписному блоці"
@@
-"Кількість людей, які самоідентифікуються як «чорношкірі» в цьому кварталі"
+"Кількість людей, які самоідентифікуються як «чорношкірі» у переписному блоці"
@@
-"Кількість людей, які самоідентифікуються як «корінні американці» в цьому "
-"кварталі"
+"Кількість людей, які самоідентифікуються як «корінні американці» у "
+"переписному блоці"Also applies to: 71-74, 81-84
🤖 Prompt for AI Agents
In postgis-intro/sources/locale/uk/LC_MESSAGES/simple_sql_exercises.po around
lines 63-65 (and also check 71-74, 81-84), the term "кварталі" is inconsistent
with earlier use of "переписному блоці"; update the translation strings to use
"переписному блоці" (or the appropriate grammatical form) so the term for
“block” is uniform across all affected msgstr entries, preserving surrounding
punctuation and quotation marks.
postgis-intro/sources/locale/uk/LC_MESSAGES/simple_sql_exercises.po
Outdated
Show resolved
Hide resolved
postgis-intro/sources/locale/uk/LC_MESSAGES/simple_sql_exercises.po
Outdated
Show resolved
Hide resolved
| #: ../../en/simple_sql_exercises.rst:38 | ||
| msgid "And, here are some common SQL aggregation functions you might find useful:" | ||
| msgstr "" | ||
|
|
||
| #: ../../en/simple_sql_exercises.rst:40 | ||
| msgid "avg() - the average (mean) of the values in a set of records" | ||
| msgstr "" | ||
|
|
||
| #: ../../en/simple_sql_exercises.rst:41 | ||
| msgid "sum() - the sum of the values in a set of records" | ||
| msgstr "" | ||
|
|
||
| #: ../../en/simple_sql_exercises.rst:42 | ||
| msgid "count() - the number of records in a set of records" | ||
| msgstr "" | ||
|
|
There was a problem hiding this comment.
Localize the aggregation functions section; keep code and semantics intact
These are currently empty; provide UA versions and preserve function names.
msgid "And, here are some common SQL aggregation functions you might find useful:"
-msgstr ""
+msgstr "А ось кілька поширених агрегатних функцій SQL, які можуть стати в пригоді:"
@@
msgid "avg() - the average (mean) of the values in a set of records"
-msgstr ""
+msgstr "avg() — середнє (арифметичне) значення для набору записів"
@@
msgid "sum() - the sum of the values in a set of records"
-msgstr ""
+msgstr "sum() — сума значень у наборі записів"
@@
msgid "count() - the number of records in a set of records"
-msgstr ""
+msgstr "count() — кількість записів у наборі записів"📝 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.
| #: ../../en/simple_sql_exercises.rst:38 | |
| msgid "And, here are some common SQL aggregation functions you might find useful:" | |
| msgstr "" | |
| #: ../../en/simple_sql_exercises.rst:40 | |
| msgid "avg() - the average (mean) of the values in a set of records" | |
| msgstr "" | |
| #: ../../en/simple_sql_exercises.rst:41 | |
| msgid "sum() - the sum of the values in a set of records" | |
| msgstr "" | |
| #: ../../en/simple_sql_exercises.rst:42 | |
| msgid "count() - the number of records in a set of records" | |
| msgstr "" | |
| #: ../../en/simple_sql_exercises.rst:38 | |
| msgid "And, here are some common SQL aggregation functions you might find useful:" | |
| msgstr "А ось кілька поширених агрегатних функцій SQL, які можуть стати в пригоді:" | |
| #: ../../en/simple_sql_exercises.rst:40 | |
| msgid "avg() - the average (mean) of the values in a set of records" | |
| msgstr "avg() — середнє (арифметичне) значення для набору записів" | |
| #: ../../en/simple_sql_exercises.rst:41 | |
| msgid "sum() - the sum of the values in a set of records" | |
| msgstr "sum() — сума значень у наборі записів" | |
| #: ../../en/simple_sql_exercises.rst:42 | |
| msgid "count() - the number of records in a set of records" | |
| msgstr "count() — кількість записів у наборі записів" |
🤖 Prompt for AI Agents
In postgis-intro/sources/locale/uk/LC_MESSAGES/simple_sql_exercises.po around
lines 141 to 156, the msgstr entries for the aggregation functions and the lead
sentence are empty; provide Ukrainian translations while preserving function
names and code semantics (do not translate avg(), sum(), count()). Replace the
empty msgstr for the lead sentence with a natural Ukrainian equivalent, and for
each function line provide a concise Ukrainian description that keeps the
function name and hyphenated explanation format (e.g., "avg() - середнє (mean)
значення в наборі записів"), ensuring grammar and punctuation match surrounding
PO entries.
| #: ../../en/simple_sql_exercises.rst:44 | ||
| msgid "Now the questions:" | ||
| msgstr "" | ||
|
|
||
| #: ../../en/simple_sql_exercises.rst:46 | ||
| msgid "**How many records are in the nyc_streets table?**" | ||
| msgstr "" | ||
|
|
||
| #: ../../en/simple_sql_exercises.rst:57 | ||
| msgid "**How many streets in NYC start with ‘B’?**" | ||
| msgstr "" | ||
|
|
There was a problem hiding this comment.
Translate the section header and first questions; preserve inline code and typography
Keep table names in code-literals and maintain bold styling.
msgid "Now the questions:"
-msgstr ""
+msgstr "Тепер запитання:"
@@
msgid "**How many records are in the nyc_streets table?**"
-msgstr ""
+msgstr "**Скільки записів у таблиці ``nyc_streets``?**"
@@
msgid "**How many streets in NYC start with ‘B’?**"
-msgstr ""
+msgstr "**Скільки вулиць у Нью-Йорку починаються на «B»?**"🤖 Prompt for AI Agents
In postgis-intro/sources/locale/uk/LC_MESSAGES/simple_sql_exercises.po around
lines 157 to 168, the translations for the section header "Now the questions:"
and the first two questions are empty; provide Ukrainian translations while
preserving the markdown/typography: keep table names like `nyc_streets` in
code-literals, retain the bold markers **...** around questions, and preserve
special quotes (use the same ‘ ’ characters). Replace msgstr "" with the
corresponding Ukrainian strings that mirror the original formatting.
| #: ../../en/simple_sql_exercises.rst:70 | ||
| msgid "**What is the population of the City of New York?**" | ||
| msgstr "" | ||
|
|
||
| #: ../../en/simple_sql_exercises.rst:83 | ||
| msgid "What is this ``AS``? You can give a table or a column another name by using an alias. Aliases can make queries easier to both write and to read. So instead of our outputted column name as ``sum`` we write it **AS** the more readable ``population``." | ||
| msgstr "" | ||
|
|
There was a problem hiding this comment.
Add missing translations; keep SQL keyword formatting
Provide a natural UA phrasing and preserve AS and code literals.
msgid "**What is the population of the City of New York?**"
-msgstr ""
+msgstr "**Яке населення міста Нью-Йорк?**"
@@
msgid "What is this ``AS``? You can give a table or a column another name by using an alias. Aliases can make queries easier to both write and to read. So instead of our outputted column name as ``sum`` we write it **AS** the more readable ``population``."
-msgstr ""
+msgstr ""
+"Що таке ``AS``? Ви можете надати таблиці або стовпцю іншу назву за допомогою "
+"псевдоніма. Псевдоніми спрощують написання й читання запитів. Тож замість "
+"імені виведеного стовпця ``sum`` ми запишемо його як більш читабельне "
+"``population``."📝 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.
| #: ../../en/simple_sql_exercises.rst:70 | |
| msgid "**What is the population of the City of New York?**" | |
| msgstr "" | |
| #: ../../en/simple_sql_exercises.rst:83 | |
| msgid "What is this ``AS``? You can give a table or a column another name by using an alias. Aliases can make queries easier to both write and to read. So instead of our outputted column name as ``sum`` we write it **AS** the more readable ``population``." | |
| msgstr "" | |
| #: ../../en/simple_sql_exercises.rst:70 | |
| msgid "**What is the population of the City of New York?**" | |
| msgstr "**Яке населення міста Нью-Йорк?**" | |
| #: ../../en/simple_sql_exercises.rst:83 | |
| msgid "What is this ``AS``? You can give a table or a column another name by using an alias. Aliases can make queries easier to both write and to read. So instead of our outputted column name as ``sum`` we write it **AS** the more readable ``population``." | |
| msgstr "" | |
| "Що таке ``AS``? Ви можете надати таблиці або стовпцю іншу назву за допомогою " | |
| "псевдоніма. Псевдоніми спрощують написання й читання запитів. Тож замість " | |
| "імені виведеного стовпця ``sum`` ми запишемо його як більш читабельне " | |
| "``population``." |
🤖 Prompt for AI Agents
In postgis-intro/sources/locale/uk/LC_MESSAGES/simple_sql_exercises.po around
lines 169 to 176, the two msgstr entries are empty; add natural Ukrainian
translations for the two msgid strings while preserving inline code formatting
and the SQL keyword ``AS`` exactly as-is (do not translate or remove backticks),
and ensure quoted code literals remain wrapped in `` backticks. Provide fluent
UA phrasing for the question about New York population and for the explanatory
sentence about aliases and ``AS``.
| #: ../../en/simple_sql_exercises.rst:85 | ||
| msgid "**What is the population of the Bronx?**" | ||
| msgstr "" | ||
|
|
||
| #: ../../en/simple_sql_exercises.rst:98 | ||
| msgid "**How many \"neighborhoods\" are in each borough?**" | ||
| msgstr "" | ||
|
|
||
| #: ../../en/simple_sql_exercises.rst:118 | ||
| msgid "**For each borough, what percentage of the population is white?**" | ||
| msgstr "" | ||
|
|
There was a problem hiding this comment.
Translate remaining questions for completeness
Ensure consistent terminology for “боро” and people categories.
msgid "**What is the population of the Bronx?**"
-msgstr ""
+msgstr "**Яке населення Бронкса?**"
@@
msgid "**How many \"neighborhoods\" are in each borough?**"
-msgstr ""
+msgstr "**Скільки «районів» у кожному боро?**"
@@
msgid "**For each borough, what percentage of the population is white?**"
-msgstr ""
+msgstr "**Який відсоток населення, що самоідентифікується як «білі», у кожному боро?**"📝 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.
| #: ../../en/simple_sql_exercises.rst:85 | |
| msgid "**What is the population of the Bronx?**" | |
| msgstr "" | |
| #: ../../en/simple_sql_exercises.rst:98 | |
| msgid "**How many \"neighborhoods\" are in each borough?**" | |
| msgstr "" | |
| #: ../../en/simple_sql_exercises.rst:118 | |
| msgid "**For each borough, what percentage of the population is white?**" | |
| msgstr "" | |
| #: ../../en/simple_sql_exercises.rst:85 | |
| msgid "**What is the population of the Bronx?**" | |
| msgstr "**Яке населення Бронкса?**" | |
| #: ../../en/simple_sql_exercises.rst:98 | |
| msgid "**How many \"neighborhoods\" are in each borough?**" | |
| msgstr "**Скільки «районів» у кожному боро?**" | |
| #: ../../en/simple_sql_exercises.rst:118 | |
| msgid "**For each borough, what percentage of the population is white?**" | |
| msgstr "**Який відсоток населення, що самоідентифікується як «білі», у кожному боро?**" |
🤖 Prompt for AI Agents
In postgis-intro/sources/locale/uk/LC_MESSAGES/simple_sql_exercises.po around
lines 177 to 188, the three msgid entries for the remaining questions are
missing Ukrainian translations; add msgstr translations for each line using
consistent terminology (use a single chosen Ukrainian term for "borough" — e.g.,
«боро» or preferably «район/боро» consistently across file — and consistent
translations for population categories such as «біле населення»), ensuring the
translations mirror the emphasis/formatting (double asterisks and quoted
“neighborhoods”) and grammatical correctness.
Currently translated at 98.9% (93 of 94 strings) Translation: postgis-workshop/about_data Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/about_data/uk/
Currently translated at 32.5% (14 of 43 strings) Translation: postgis-workshop/simple_sql_exercises Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/simple_sql_exercises/uk/
Currently translated at 100.0% (94 of 94 strings) Translation: postgis-workshop/about_data Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/about_data/uk/
Currently translated at 37.2% (16 of 43 strings) Translation: postgis-workshop/simple_sql_exercises Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/simple_sql_exercises/uk/
Currently translated at 37.2% (16 of 43 strings) Translation: postgis-workshop/simple_sql_exercises Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/simple_sql_exercises/uk/
Currently translated at 62.7% (27 of 43 strings) Translation: postgis-workshop/simple_sql_exercises Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/simple_sql_exercises/uk/
Currently translated at 62.7% (27 of 43 strings) Translation: postgis-workshop/simple_sql_exercises Translate-URL: https://weblate.osgeo.org/projects/postgis-workshop/simple_sql_exercises/uk/
Translations update from OSGeo Weblate for postgis-workshop/index.
It also includes following components:
postgis-workshop/geometry_returning
postgis-workshop/projection_exercises
postgis-workshop/simple_sql_exercises
postgis-workshop/tuning
postgis-workshop/backup
postgis-workshop/license
postgis-workshop/installation
postgis-workshop/equality
postgis-workshop/joins_advanced
postgis-workshop/topology
postgis-workshop/security
postgis-workshop/clusterindex
postgis-workshop/linear_referencing
postgis-workshop/about_data
postgis-workshop/upgrades
postgis-workshop/3d
postgis-workshop/welcome
postgis-workshop/spatial_relationships_exercises
postgis-workshop/de9im
postgis-workshop/spatial_relationships
postgis-workshop/simple_sql
postgis-workshop/schemas
postgis-workshop/creating_db
postgis-workshop/history_tracking
postgis-workshop/geometries_exercises
postgis-workshop/projection
postgis-workshop/geometry_returning_exercises
postgis-workshop/topology_base_types
postgis-workshop/joins
postgis-workshop/postgis-functions
postgis-workshop/introduction
postgis-workshop/topology_topo_types
postgis-workshop/joins_exercises
postgis-workshop/glossary 1
postgis-workshop/geography
postgis-workshop/validity
postgis-workshop/geography_exercises
postgis-workshop/indexing
postgis-workshop/geometries
postgis-workshop/advanced_geometry_construction
postgis-workshop/knn
postgis-workshop/loading_data
postgis-workshop/rasters
Current translation status: