Translations update from OSGeo Weblate - #3119
Open
osgeoweblate wants to merge 1 commit into
Open
Conversation
Contributor
WalkthroughUpdated German, Spanish, Japanese, Korean, Swedish, and Simplified Chinese PO catalogs with experimental server-crash warnings, refreshed creation dates, and pgRouting 4.0.2 release-notes entries. ChangesTranslation catalog updates
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
Suggested labels: Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@locale/es/LC_MESSAGES/pgrouting_doc_strings.po`:
- Around line 346-350: Translate the two empty Spanish catalog entries for
“Possible server crash” and “These functions might create a server crash” in the
PO file, or explicitly mark them as intentionally untranslated if no translation
is available. Keep the existing msgid values unchanged and ensure both msgstr
fields are handled.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: 8869a720-7feb-4fa2-a9ea-5e989a82b647
📒 Files selected for processing (6)
locale/de/LC_MESSAGES/pgrouting_doc_strings.polocale/es/LC_MESSAGES/pgrouting_doc_strings.polocale/ja/LC_MESSAGES/pgrouting_doc_strings.polocale/ko/LC_MESSAGES/pgrouting_doc_strings.polocale/sv/LC_MESSAGES/pgrouting_doc_strings.polocale/zh_Hans/LC_MESSAGES/pgrouting_doc_strings.po
osgeoweblate
force-pushed
the
weblate-pgrouting-pgrouting-develop
branch
from
July 24, 2026 02:47
9f07695 to
b43b504
Compare
Contributor
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@locale/ja/LC_MESSAGES/pgrouting_doc_strings.po`:
- Around line 365-370: Translate the Japanese `msgstr` entries for “Possible
server crash” and “These functions might create a server crash” in the locale
file, preserving the warning meaning and the existing gettext message pairing.
In `@locale/ko/LC_MESSAGES/pgrouting_doc_strings.po`:
- Around line 346-351: Translate the two new warning entries in the Korean
catalog by replacing the empty msgstr values for “Possible server crash” and
“These functions might create a server crash” with appropriate Korean
translations, preserving the existing gettext entry structure.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 8f6a95c8-c586-4225-9699-d306f147a1f6
📒 Files selected for processing (6)
locale/de/LC_MESSAGES/pgrouting_doc_strings.polocale/es/LC_MESSAGES/pgrouting_doc_strings.polocale/ja/LC_MESSAGES/pgrouting_doc_strings.polocale/ko/LC_MESSAGES/pgrouting_doc_strings.polocale/sv/LC_MESSAGES/pgrouting_doc_strings.polocale/zh_Hans/LC_MESSAGES/pgrouting_doc_strings.po
Comment on lines
+365
to
+370
| msgid "Possible server crash" | ||
| msgstr "" | ||
|
|
||
| msgid "These functions might create a server crash" | ||
| msgstr "" | ||
|
|
Contributor
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Translate the new server-crash warnings.
Both msgstr values are empty, so Japanese documentation will display the English warnings. These are important safety notices for experimental functions and should be localized before merge.
Suggested translations
msgid "Possible server crash"
-msgstr ""
+msgstr "サーバーがクラッシュする可能性があります"
msgid "These functions might create a server crash"
-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.
Suggested change
| msgid "Possible server crash" | |
| msgstr "" | |
| msgid "These functions might create a server crash" | |
| msgstr "" | |
| msgid "Possible server crash" | |
| msgstr "サーバーがクラッシュする可能性があります" | |
| msgid "These functions might create a server crash" | |
| msgstr "これらの関数はサーバーをクラッシュさせる可能性があります" |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@locale/ja/LC_MESSAGES/pgrouting_doc_strings.po` around lines 365 - 370,
Translate the Japanese `msgstr` entries for “Possible server crash” and “These
functions might create a server crash” in the locale file, preserving the
warning meaning and the existing gettext message pairing.
Comment on lines
+346
to
+351
| msgid "Possible server crash" | ||
| msgstr "" | ||
|
|
||
| msgid "These functions might create a server crash" | ||
| msgstr "" | ||
|
|
Contributor
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Locate and inspect the referenced message entries context without modifying files.
sed -n '338,356p' locale/ko/LC_MESSAGES/pgrouting_doc_strings.po | cat -n
printf '\n--- nearby related entries ---\n'
rg -n 'Possible server crash|These functions might create a server crash|server crash|서버 충돌' locale/ko/LC_MESSAGES/pgrouting_doc_strings.po locale -g '*.po' || trueRepository: pgRouting/pgrouting
Length of output: 4146
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Inspect the referenced message entries context and nearby related strings.
sed -n '338,356p' locale/ko/LC_MESSAGES/pgrouting_doc_strings.po | cat -n
printf '\n--- related search in repository ---\n'
rg -n 'Possible server crash|These functions might create a server crash|server crash|서버 충돌' locale -g '*.po' || trueRepository: pgRouting/pgrouting
Length of output: 3702
Translate the new Korean warning strings.
Both entries have empty msgstr values, so the Korean documentation falls back to English for these server-crash warnings. Add Korean translations before merging.
Proposed translation
msgid "Possible server crash"
-msgstr ""
+msgstr "서버 충돌 가능성"
msgid "These functions might create a server crash"
-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.
Suggested change
| msgid "Possible server crash" | |
| msgstr "" | |
| msgid "These functions might create a server crash" | |
| msgstr "" | |
| msgid "Possible server crash" | |
| msgstr "서버 충돌 가능성" | |
| msgid "These functions might create a server crash" | |
| msgstr "이러한 함수는 서버 충돌을 일으킬 수 있습니다" |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@locale/ko/LC_MESSAGES/pgrouting_doc_strings.po` around lines 346 - 351,
Translate the two new warning entries in the Korean catalog by replacing the
empty msgstr values for “Possible server crash” and “These functions might
create a server crash” with appropriate Korean translations, preserving the
existing gettext entry structure.
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Update translation files Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Co-authored-by: Weblate <noreply@weblate.org> Translate-URL: https://weblate.osgeo.org/projects/pgrouting/pgrouting-develop/ Translation: pgRouting/pgRouting
osgeoweblate
force-pushed
the
weblate-pgrouting-pgrouting-develop
branch
from
July 28, 2026 14:48
b43b504 to
b64825b
Compare
Contributor
There was a problem hiding this comment.
Actionable comments posted: 6
♻️ Duplicate comments (1)
locale/es/LC_MESSAGES/pgrouting_doc_strings.po (1)
346-350: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick winTranslate the new warning messages.
Both Spanish
msgstrvalues are empty, so users will see the English warnings. This repeats the previously reported issue; add Spanish translations or intentionally keep these entries untranslated with an explicit workflow decision.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@locale/es/LC_MESSAGES/pgrouting_doc_strings.po` around lines 346 - 350, Provide Spanish translations for the empty msgstr entries corresponding to “Possible server crash” and “These functions might create a server crash” in the localization file, preserving the existing gettext structure and warning meaning.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@locale/es/LC_MESSAGES/pgrouting_doc_strings.po`:
- Around line 12864-12874: The Spanish fuzzy translations for the pgRouting
4.0.2 release notes are stale and reference older releases and issue numbers.
Update the three affected msgstr entries to accurately translate the
corresponding 4.0.2 release title, milestone 4.0.2 link, and issue `#3110`
description, then remove each fuzzy marker so the corrected translations are
accepted.
In `@locale/ja/LC_MESSAGES/pgrouting_doc_strings.po`:
- Around line 13054-13062: Translate the three empty msgstr entries in the 4.0.2
release-notes section into Japanese, covering the release heading, milestone
description, and `#3110` issue description. Preserve all reStructuredText links,
issue numbers, URLs, and inline markup exactly while translating only the
surrounding prose.
In `@locale/ko/LC_MESSAGES/pgrouting_doc_strings.po`:
- Around line 12952-12960: Translate the three new 4.0.2 release-note entries in
the Korean PO file: the “pgRouting 4.0.2 Release Notes” title, the milestone
reference, and the `#3110` pgr_dijkstraVia entry. Populate each corresponding
msgstr while preserving the issue number, URL, markup, and technical meaning.
In `@locale/sv/LC_MESSAGES/pgrouting_doc_strings.po`:
- Line 10: Update the PO-Revision-Date metadata in the Swedish translation
catalog to the actual timestamp for this translation commit, keeping it
consistent with the newly added Swedish translations and the updated
POT-Creation-Date.
- Around line 12755-12765: Update the Swedish msgstr values for “pgRouting 4.0.2
Release Notes,” the 4.0.2 GitHub milestone entry, and issue `#3110` to accurately
translate their current msgid content rather than older release notes; after
verifying each translation, remove the `fuzzy` flags for these entries.
In `@locale/zh_Hans/LC_MESSAGES/pgrouting_doc_strings.po`:
- Around line 351-356: Translate the new warning strings in the locale’s PO
entries: provide reviewed Simplified Chinese msgstr values for “Possible server
crash” and “These functions might create a server crash,” preserving their
warning meaning and leaving the msgid entries unchanged.
---
Duplicate comments:
In `@locale/es/LC_MESSAGES/pgrouting_doc_strings.po`:
- Around line 346-350: Provide Spanish translations for the empty msgstr entries
corresponding to “Possible server crash” and “These functions might create a
server crash” in the localization file, preserving the existing gettext
structure and warning meaning.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 10df641d-508a-459b-b4ad-40bc95a2add3
📒 Files selected for processing (6)
locale/de/LC_MESSAGES/pgrouting_doc_strings.polocale/es/LC_MESSAGES/pgrouting_doc_strings.polocale/ja/LC_MESSAGES/pgrouting_doc_strings.polocale/ko/LC_MESSAGES/pgrouting_doc_strings.polocale/sv/LC_MESSAGES/pgrouting_doc_strings.polocale/zh_Hans/LC_MESSAGES/pgrouting_doc_strings.po
Comment on lines
+12864
to
+12874
| #, fuzzy | ||
| msgid "pgRouting 4.0.2 Release Notes" | ||
| msgstr "Notas de la versión 3.0.1 de pgRouting" | ||
|
|
||
| #, fuzzy | ||
| msgid "To see all issues & pull requests closed by this release see the `Github milestone for 4.0.2 <https://github.com/pgRouting/pgrouting/issues?utf8=%E2%9C%93&q=milestone%3A%22Release%204.0.2%22>`__" | ||
| msgstr "Para ver todos los problemas y solicitudes de extracción cerrados para ésta versión, consulte la `Github milestone for 4.0.0 <https://github.com/pgRouting/pgrouting/issues?utf8=%E2%9C%93&q=milestone%3A%22Release%204.0.0%22>`__" | ||
|
|
||
| #, fuzzy | ||
| msgid "`#3110 <https://github.com/pgRouting/pgrouting/issues/3110>`__: pgr_dijkstraVia throws std::bad_alloc when a node does not exist" | ||
| msgstr "`#1640 <https://github.com/pgRouting/pgrouting/issues/1640>`__: pgr_withPoints falla cuando points_sql está vacía" |
Contributor
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Correct the stale fuzzy translations before accepting them.
These msgstr values still reference release 3.0.1, milestone 4.0.0, and issue #1640 instead of release 4.0.2 and issue #3110. They are currently protected by fuzzy, but removing that marker would publish incorrect Spanish release notes.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@locale/es/LC_MESSAGES/pgrouting_doc_strings.po` around lines 12864 - 12874,
The Spanish fuzzy translations for the pgRouting 4.0.2 release notes are stale
and reference older releases and issue numbers. Update the three affected msgstr
entries to accurately translate the corresponding 4.0.2 release title, milestone
4.0.2 link, and issue `#3110` description, then remove each fuzzy marker so the
corrected translations are accepted.
Comment on lines
+13054
to
+13062
| msgid "pgRouting 4.0.2 Release Notes" | ||
| msgstr "" | ||
|
|
||
| msgid "To see all issues & pull requests closed by this release see the `Github milestone for 4.0.2 <https://github.com/pgRouting/pgrouting/issues?utf8=%E2%9C%93&q=milestone%3A%22Release%204.0.2%22>`__" | ||
| msgstr "" | ||
|
|
||
| msgid "`#3110 <https://github.com/pgRouting/pgrouting/issues/3110>`__: pgr_dijkstraVia throws std::bad_alloc when a node does not exist" | ||
| msgstr "" | ||
|
|
Contributor
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Translate the new 4.0.2 release notes.
All three Japanese msgstr values are empty, so this release-notes section will appear in English in the Japanese documentation. Preserve the milestone and issue markup while translating the surrounding text.
Suggested translations
msgid "pgRouting 4.0.2 Release Notes"
-msgstr ""
+msgstr "pgRouting 4.0.2 リリースノート"
msgid "To see all issues & pull requests closed by this release see the `Github milestone for 4.0.2 <https://github.com/pgRouting/pgrouting/issues?utf8=%E2%9C%93&q=milestone%3A%22Release%204.0.2%22>`__"
-msgstr ""
+msgstr "このリリースでクローズされたすべてのイシューとプルリクエストについては、`4.0.2 の GitHub マイルストーン <https://github.com/pgRouting/pgrouting/issues?utf8=%E2%9C%93&q=milestone%3A%22Release%204.0.2%22>`__をご覧ください。"
msgid "`#3110 <https://github.com/pgRouting/pgrouting/issues/3110>`__: pgr_dijkstraVia throws std::bad_alloc when a node does not exist"
-msgstr ""
+msgstr "`#3110 <https://github.com/pgRouting/pgrouting/issues/3110>`__: ノードが存在しない場合、pgr_dijkstraVia が std::bad_alloc を発生させる"📝 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.
Suggested change
| msgid "pgRouting 4.0.2 Release Notes" | |
| msgstr "" | |
| msgid "To see all issues & pull requests closed by this release see the `Github milestone for 4.0.2 <https://github.com/pgRouting/pgrouting/issues?utf8=%E2%9C%93&q=milestone%3A%22Release%204.0.2%22>`__" | |
| msgstr "" | |
| msgid "`#3110 <https://github.com/pgRouting/pgrouting/issues/3110>`__: pgr_dijkstraVia throws std::bad_alloc when a node does not exist" | |
| msgstr "" | |
| msgid "pgRouting 4.0.2 Release Notes" | |
| msgstr "pgRouting 4.0.2 リリースノート" | |
| msgid "To see all issues & pull requests closed by this release see the `Github milestone for 4.0.2 <https://github.com/pgRouting/pgrouting/issues?utf8=%E2%9C%93&q=milestone%3A%22Release%204.0.2%22>`__" | |
| msgstr "このリリースでクローズされたすべてのイシューとプルリクエストについては、`4.0.2 の GitHub マイルストーン <https://github.com/pgRouting/pgrouting/issues?utf8=%E2%9C%93&q=milestone%3A%22Release%204.0.2%22>`__をご覧ください。" | |
| msgid "`#3110 <https://github.com/pgRouting/pgrouting/issues/3110>`__: pgr_dijkstraVia throws std::bad_alloc when a node does not exist" | |
| msgstr "`#3110 <https://github.com/pgRouting/pgrouting/issues/3110>`__: ノードが存在しない場合、pgr_dijkstraVia が std::bad_alloc を発生させる" |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@locale/ja/LC_MESSAGES/pgrouting_doc_strings.po` around lines 13054 - 13062,
Translate the three empty msgstr entries in the 4.0.2 release-notes section into
Japanese, covering the release heading, milestone description, and `#3110` issue
description. Preserve all reStructuredText links, issue numbers, URLs, and
inline markup exactly while translating only the surrounding prose.
Comment on lines
+12952
to
+12960
| msgid "pgRouting 4.0.2 Release Notes" | ||
| msgstr "" | ||
|
|
||
| msgid "To see all issues & pull requests closed by this release see the `Github milestone for 4.0.2 <https://github.com/pgRouting/pgrouting/issues?utf8=%E2%9C%93&q=milestone%3A%22Release%204.0.2%22>`__" | ||
| msgstr "" | ||
|
|
||
| msgid "`#3110 <https://github.com/pgRouting/pgrouting/issues/3110>`__: pgr_dijkstraVia throws std::bad_alloc when a node does not exist" | ||
| msgstr "" | ||
|
|
Contributor
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Translate the new 4.0.2 release-note entries.
The release-note title, milestone reference, and #3110 entry all have empty Korean translations, causing these additions to fall back to English.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@locale/ko/LC_MESSAGES/pgrouting_doc_strings.po` around lines 12952 - 12960,
Translate the three new 4.0.2 release-note entries in the Korean PO file: the
“pgRouting 4.0.2 Release Notes” title, the milestone reference, and the `#3110`
pgr_dijkstraVia entry. Populate each corresponding msgstr while preserving the
issue number, URL, markup, and technical meaning.
| "Project-Id-Version: pgRouting v4.1\n" | ||
| "Report-Msgid-Bugs-To: \n" | ||
| "POT-Creation-Date: 2026-06-10 19:05+0000\n" | ||
| "POT-Creation-Date: 2026-07-27 19:59+0000\n" |
Contributor
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Update the catalog revision timestamp.
Line [10] changes the source-template timestamp, but PO-Revision-Date remains 2025-12-08 even though this commit adds Swedish translations. Set it to the actual revision timestamp so the catalog metadata is consistent.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@locale/sv/LC_MESSAGES/pgrouting_doc_strings.po` at line 10, Update the
PO-Revision-Date metadata in the Swedish translation catalog to the actual
timestamp for this translation commit, keeping it consistent with the newly
added Swedish translations and the updated POT-Creation-Date.
Comment on lines
+12755
to
+12765
| #, fuzzy | ||
| msgid "pgRouting 4.0.2 Release Notes" | ||
| msgstr "Versionsinformation för pgRouting 3.0.1" | ||
|
|
||
| #, fuzzy | ||
| msgid "To see all issues & pull requests closed by this release see the `Github milestone for 4.0.2 <https://github.com/pgRouting/pgrouting/issues?utf8=%E2%9C%93&q=milestone%3A%22Release%204.0.2%22>`__" | ||
| msgstr "För att se alla problem och pull requests som stängts av denna release, se `Github milstolpe för 4.0.0 <https://github.com/pgRouting/pgrouting/issues?utf8=%E2%9C%93&q=milestone%3A%22Release%204.0.0%22>`__" | ||
|
|
||
| #, fuzzy | ||
| msgid "`#3110 <https://github.com/pgRouting/pgrouting/issues/3110>`__: pgr_dijkstraVia throws std::bad_alloc when a node does not exist" | ||
| msgstr "`#1640 <https://github.com/pgRouting/pgrouting/issues/1640>`__: pgr_withPoints misslyckas när points_sql är tom" |
Contributor
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "Repository files around targeted po:"
fd -a 'pgrouting_doc_strings\.po$' . || true
po_file="$(fd 'pgrouting_doc_strings\.po$' . | head -n1 || true)"
if [ -n "${po_file:-}" ]; then
echo "Target PO: $po_file"
echo "Lines 12745-12775:"
sed -n '12745,12775p' "$po_file" | nl -ba -v12745
fi
echo
echo "Search release notes source for 4.0.2 and issue references:"
rg -n "4\.0\.2|3\.0\.1|3110|1640|Release 4\.0\.2" -S . --glob '!*build*' --glob '!*dist*' --glob '!*.po' | head -n 80 || true
if [ -n "${po_file:-}" ]; then
echo
echo "All occurrences of the matched identifiers in the PO header/context:"
rg -n "pgRouting 4\.0\.2 Release Notes|github.com/pgRouting/pgrouting/issues/3110|github.com/pgRouting/pgrouting/issues/1640" "$po_file" || true
fiRepository: pgRouting/pgrouting
Length of output: 781
🏁 Script executed:
#!/bin/bash
set -euo pipefail
po_file="./locale/sv/LC_MESSAGES/pgrouting_doc_strings.po"
echo "Target PO: $po_file"
echo "Targeted Swedish entries:"
sed -n '12752,12770p' "$po_file"
echo
echo "Targeted source release notes (doc/src/release_notes.rst if present):"
if [ -f doc/src/release_notes.rst ]; then
sed -n '60,90p' doc/src/release_notes.rst
fi
echo
echo "Occurrences in release docs/source:"
rg -n "pgRouting 4\.0\.2 Release Notes|Release 4\.0\.2|github\.com/pgRouting/pgrouting/issues\?|issue/3110|issue/1640|milestone%3A%22Release%204\.0\.2%22" doc src --glob '!*.po' --glob '!build/**' --glob '!dist/**' || true
echo
echo "Occurrences in Swedish PO:"
rg -n "pgRouting 4\.0\.2 Release Notes|3\.0\.1|milestone.*4\.0\.2|issue/3110|issue/1640" "$po_file" || trueRepository: pgRouting/pgrouting
Length of output: 4014
Update the stale pgRouting 4.0.2 Swedish release-note entries.
The source release notes are for pgRouting 4.0.2 and issue #3110, but the Swedish msgstr values still copy content from older releases/milestones. Add a Swedish translation for the 4.0.2 entries and remove fuzzy after review.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@locale/sv/LC_MESSAGES/pgrouting_doc_strings.po` around lines 12755 - 12765,
Update the Swedish msgstr values for “pgRouting 4.0.2 Release Notes,” the 4.0.2
GitHub milestone entry, and issue `#3110` to accurately translate their current
msgid content rather than older release notes; after verifying each translation,
remove the `fuzzy` flags for these entries.
Comment on lines
+351
to
+356
| msgid "Possible server crash" | ||
| msgstr "" | ||
|
|
||
| msgid "These functions might create a server crash" | ||
| msgstr "" | ||
|
|
Contributor
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Translate the new warning strings.
Empty msgstr values leave these warnings in English in the Simplified Chinese documentation. Add reviewed Chinese translations before shipping this locale.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@locale/zh_Hans/LC_MESSAGES/pgrouting_doc_strings.po` around lines 351 - 356,
Translate the new warning strings in the locale’s PO entries: provide reviewed
Simplified Chinese msgstr values for “Possible server crash” and “These
functions might create a server crash,” preserving their warning meaning and
leaving the msgid entries unchanged.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Translations update from OSGeo Weblate for pgRouting/pgRouting.
Current translation status:
Reminder: Do not squash, do a rebase
Summary by CodeRabbit
#3110.