chore: add updated po files #531
Conversation
WalkthroughThis pull request updates translation files across multiple locales, advancing POT creation dates from July to November 2025, updating version references (Dash Core 22.1.3→23.0.0, Dashmate, Dash Evo Tool), renaming documentation identifiers (ipAndPort→coreP2PAddrs), and refactoring content formatting in earning-spending documentation. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Notes:
Poem
Pre-merge checks and finishing touches✅ Passed checks (3 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}
There was a problem hiding this comment.
Actionable comments posted: 0
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (8)
locale/fr/LC_MESSAGES/docs/user/introduction/about.po (1)
214-220: Update French translation to use the correct Evolution document URL.The new URL at
media.dash.orgis valid and accessible (HTTP 200, PDF content confirmed). The old URL atwww.dash.orgis broken—it redirects to the homepage (HTTP 302). Update the French translation on lines 219-220 to replacewww.dash.orgwithmedia.dash.orgto match the corrected English source and ensure the French documentation points to the actual document instead of a redirect loop.locale/el/LC_MESSAGES/docs/user/masternodes/setup.po (1)
576-576: Remove remaining active ipAndPort entries in setup.po (vi, ru, it, fr locales) to complete the refactoring.Verification found active ipAndPort entries that should be cleaned up:
locale/vi/LC_MESSAGES/docs/user/masternodes/setup.po:796locale/ru/LC_MESSAGES/docs/user/masternodes/setup.po:1008locale/it/LC_MESSAGES/docs/user/masternodes/setup.po:1010locale/fr/LC_MESSAGES/docs/user/masternodes/setup.po:993Most locales have correctly moved ipAndPort to obsolete entries (#~), but these four locales retain active msgids alongside the new coreP2PAddrs. Note: maintenance.po files still contain 15 active ipAndPort entries across all locales—verify if this file should also be updated as part of this refactoring.
locale/de/LC_MESSAGES/docs/user/network/dash-evo-tool/index.po (2)
961-966: Fuzzy mistranslation: “Token Information”.Current msgstr “Konfiguration” is inaccurate. Recommend correcting or clearing until translated.
- msgstr "Konfiguration" + msgstr "Token-Informationen"
1168-1174: Fuzzy mistranslation: “Enables all actions.”“Installation” is unrelated. Please fix.
- msgstr "Installation" + msgstr "Ermöglicht alle Aktionen."locale/es/LC_MESSAGES/docs/user/network/dash-evo-tool/index.po (2)
961-966: Traducción difusa incorrecta: “Token Information”.“Configuración” no corresponde. Sugerencia:
- msgstr "Configuración" + msgstr "Información del token"
1173-1176: Traducción difusa incorrecta: “Enables all actions.”Reemplazar por:
- msgstr "Instalación" + msgstr "Habilita todas las acciones."locale/el/LC_MESSAGES/docs/user/network/dash-evo-tool/index.po (1)
1169-1173: Λανθασμένη μετάφραση (fuzzy): “Enables all actions.”“Εγκατάσταση” δεν ταιριάζει. Πρόταση:
- msgstr "Εγκατάσταση" + msgstr "Ενεργοποιεί όλες τις ενέργειες."locale/es/LC_MESSAGES/docs/user/earning-spending.po (1)
31-33: Terminología: “debit cards” → “tarjetas de débito”.Corregir la traducción del resumen.
- "Guías sobre tarjetas de crédito, conversión salarial, comercios y tiendas físicas." + "Guías sobre tarjetas de débito, conversión salarial, comercios y tiendas físicas."
🧹 Nitpick comments (17)
locale/fr/LC_MESSAGES/docs/user/introduction/about.po (1)
32-36: Note: Duplicate "roadmap" keyword in metadata.The keyword list contains "roadmap" twice (line 32-33), which is also reflected in the French translation ("feuille de route" appears twice on lines 35-36). This redundancy is present in both the English source and French translation, maintaining consistency, though it may be worth checking if this duplication is intentional in the source documentation.
locale/ar/LC_MESSAGES/docs/user/masternodes/setup-evonode.po (1)
957-964: Obsolete msgid retained for 2.0.1 — optional cleanup.
If desired, prune older obsolete blocks to keep PO size down.locale/de/LC_MESSAGES/docs/user/masternodes/setup-evonode.po (1)
951-958: Obsolete msgids — optional trim.
Consider removing older obsolete blocks to reduce churn (non-blocking).locale/es/LC_MESSAGES/docs/user/masternodes/setup-evonode.po (1)
967-974: Obsolete msgid for prior .deb — optional cleanup.
Safe to keep; you may prune to keep PO tidy.locale/es/LC_MESSAGES/docs/user/masternodes/setup.po (1)
959-961: Obsolete ipAndPort entry — optional cleanup.locale/el/LC_MESSAGES/docs/user/masternodes/setup-testnet.po (1)
816-818: Obsolete ipAndPort entry — optional cleanup.locale/en/LC_MESSAGES/docs/user/masternodes/setup.po (1)
1291-1293: Obsolete ipAndPort entry — optional cleanup.locale/ar/LC_MESSAGES/docs/user/masternodes/setup-testnet.po (1)
820-822: Obsolete ipAndPort entry — optional cleanup.locale/en/LC_MESSAGES/docs/user/masternodes/setup-testnet.po (1)
7-20: Standardize PO headers by adding language metadata to setup-testnet.po and other en/*.po files.Verification confirms inconsistency: most English PO files lack "Language: en" and "Plural-Forms: nplurals=2; plural=(n != 1);" headers, though ~12 newer files (dashmate-, integration-, and evonode-related files) include them. Adding these headers to setup-testnet.po and other older files would align with the newer standard. Harmless to defer.
locale/en/LC_MESSAGES/docs/user/network/dash-evo-tool/index.po (4)
169-174: Grammar: “a application” → “an application”.Fix in source RST so all locales inherit the correction: “it creates an application directory…”.
614-618: Typo: “chose” → “choose”.“…There you can choose to cast your votes…” in the source RST.
679-683: Grammar: missing “of”.“to view a list of current or previous contests.”
1286-1294: Grammar: add article.“On the approval screen, select the key…”
locale/en/LC_MESSAGES/docs/user/earning-spending.po (1)
119-127: External link health check (periodic).Given provider churn, periodically validate external links (Crypto.com, Change, Bitsa, SpectroCoin) to avoid dead references. I can wire a CI job to curl HEAD these URLs.
Also applies to: 141-152, 175-183, 200-207
locale/de/LC_MESSAGES/docs/user/earning-spending.po (1)
99-108: Remove unnecessary fuzzy flag.This entry is translated and accurate; drop fuzzy so it renders in DE.
-#, fuzzy msgid "" "Dash can be spent in hundreds of stores and services both online and in " "physical locations worldwide." msgstr "" "Dash kann als Zahlungsmethode in Hunderten Geschäften und Dienstleistungsbetrieben verwendet werden, sowohl online als auch in der physischen Welt."locale/es/LC_MESSAGES/docs/user/earning-spending.po (1)
229-231: Título en plural.“Tax” aquí es genérico; en ES se usa mejor “Impuestos”.
- msgstr "Impuesto" + msgstr "Impuestos"locale/de/LC_MESSAGES/docs/user/network/dash-evo-tool/index.po (1)
63-89: All v0.9.3 asset URLs verified and resolving correctly.All five platform links return HTTP 200 and are accessible. No link rot detected.
To reduce future churn across locales and prevent similar URL maintenance issues, consider extracting the version string (v0.9.3) as a substitution variable or constant in the source RST and reuse it across these download links.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (68)
locale/ar/LC_MESSAGES/docs/user/developers/insight.po(3 hunks)locale/ar/LC_MESSAGES/docs/user/earning-spending.po(9 hunks)locale/ar/LC_MESSAGES/docs/user/introduction/about.po(8 hunks)locale/ar/LC_MESSAGES/docs/user/introduction/information.po(92 hunks)locale/ar/LC_MESSAGES/docs/user/masternodes/hosting.po(10 hunks)locale/ar/LC_MESSAGES/docs/user/masternodes/setup-evonode.po(3 hunks)locale/ar/LC_MESSAGES/docs/user/masternodes/setup-testnet.po(3 hunks)locale/ar/LC_MESSAGES/docs/user/masternodes/setup.po(3 hunks)locale/ar/LC_MESSAGES/docs/user/network/dash-evo-tool/index.po(3 hunks)locale/ar/LC_MESSAGES/docs/user/network/dashmate/index.po(3 hunks)locale/ar/LC_MESSAGES/docs/user/wallets/dashcore/installation-linux.po(8 hunks)locale/ar/LC_MESSAGES/docs/user/wallets/dashcore/installation-windows.po(4 hunks)locale/ar/LC_MESSAGES/docs/user/wallets/hardware.po(20 hunks)locale/de/LC_MESSAGES/docs/user/developers/insight.po(3 hunks)locale/de/LC_MESSAGES/docs/user/earning-spending.po(9 hunks)locale/de/LC_MESSAGES/docs/user/introduction/about.po(9 hunks)locale/de/LC_MESSAGES/docs/user/introduction/information.po(58 hunks)locale/de/LC_MESSAGES/docs/user/masternodes/hosting.po(10 hunks)locale/de/LC_MESSAGES/docs/user/masternodes/setup-evonode.po(3 hunks)locale/de/LC_MESSAGES/docs/user/masternodes/setup-testnet.po(3 hunks)locale/de/LC_MESSAGES/docs/user/masternodes/setup.po(3 hunks)locale/de/LC_MESSAGES/docs/user/network/dash-evo-tool/index.po(3 hunks)locale/de/LC_MESSAGES/docs/user/network/dashmate/index.po(3 hunks)locale/de/LC_MESSAGES/docs/user/wallets/dashcore/installation-linux.po(8 hunks)locale/de/LC_MESSAGES/docs/user/wallets/dashcore/installation-windows.po(4 hunks)locale/de/LC_MESSAGES/docs/user/wallets/hardware.po(22 hunks)locale/el/LC_MESSAGES/docs/user/developers/insight.po(3 hunks)locale/el/LC_MESSAGES/docs/user/earning-spending.po(9 hunks)locale/el/LC_MESSAGES/docs/user/introduction/about.po(8 hunks)locale/el/LC_MESSAGES/docs/user/introduction/information.po(58 hunks)locale/el/LC_MESSAGES/docs/user/masternodes/hosting.po(11 hunks)locale/el/LC_MESSAGES/docs/user/masternodes/setup-evonode.po(3 hunks)locale/el/LC_MESSAGES/docs/user/masternodes/setup-testnet.po(3 hunks)locale/el/LC_MESSAGES/docs/user/masternodes/setup.po(3 hunks)locale/el/LC_MESSAGES/docs/user/network/dash-evo-tool/index.po(3 hunks)locale/el/LC_MESSAGES/docs/user/network/dashmate/index.po(3 hunks)locale/el/LC_MESSAGES/docs/user/wallets/dashcore/installation-linux.po(6 hunks)locale/el/LC_MESSAGES/docs/user/wallets/dashcore/installation-windows.po(4 hunks)locale/el/LC_MESSAGES/docs/user/wallets/hardware.po(11 hunks)locale/en/LC_MESSAGES/docs/user/developers/insight.po(3 hunks)locale/en/LC_MESSAGES/docs/user/earning-spending.po(6 hunks)locale/en/LC_MESSAGES/docs/user/introduction/about.po(3 hunks)locale/en/LC_MESSAGES/docs/user/introduction/information.po(58 hunks)locale/en/LC_MESSAGES/docs/user/masternodes/hosting.po(4 hunks)locale/en/LC_MESSAGES/docs/user/masternodes/setup-evonode.po(3 hunks)locale/en/LC_MESSAGES/docs/user/masternodes/setup-testnet.po(3 hunks)locale/en/LC_MESSAGES/docs/user/masternodes/setup.po(3 hunks)locale/en/LC_MESSAGES/docs/user/network/dash-evo-tool/index.po(3 hunks)locale/en/LC_MESSAGES/docs/user/network/dashmate/index.po(3 hunks)locale/en/LC_MESSAGES/docs/user/wallets/dashcore/installation-linux.po(6 hunks)locale/en/LC_MESSAGES/docs/user/wallets/dashcore/installation-windows.po(4 hunks)locale/en/LC_MESSAGES/docs/user/wallets/hardware.po(11 hunks)locale/es/LC_MESSAGES/docs/user/developers/insight.po(3 hunks)locale/es/LC_MESSAGES/docs/user/earning-spending.po(9 hunks)locale/es/LC_MESSAGES/docs/user/introduction/about.po(9 hunks)locale/es/LC_MESSAGES/docs/user/introduction/information.po(96 hunks)locale/es/LC_MESSAGES/docs/user/masternodes/hosting.po(11 hunks)locale/es/LC_MESSAGES/docs/user/masternodes/setup-evonode.po(3 hunks)locale/es/LC_MESSAGES/docs/user/masternodes/setup-testnet.po(3 hunks)locale/es/LC_MESSAGES/docs/user/masternodes/setup.po(3 hunks)locale/es/LC_MESSAGES/docs/user/network/dash-evo-tool/index.po(3 hunks)locale/es/LC_MESSAGES/docs/user/network/dashmate/index.po(3 hunks)locale/es/LC_MESSAGES/docs/user/wallets/dashcore/installation-linux.po(8 hunks)locale/es/LC_MESSAGES/docs/user/wallets/dashcore/installation-windows.po(4 hunks)locale/es/LC_MESSAGES/docs/user/wallets/hardware.po(22 hunks)locale/fr/LC_MESSAGES/docs/user/developers/insight.po(2 hunks)locale/fr/LC_MESSAGES/docs/user/earning-spending.po(11 hunks)locale/fr/LC_MESSAGES/docs/user/introduction/about.po(9 hunks)
🧰 Additional context used
🧠 Learnings (4)
📓 Common learnings
Learnt from: thephez
Repo: dashpay/docs PR: 525
File: docs/core/api/remote-procedure-calls-wallet.md:1737-1738
Timestamp: 2025-11-10T18:51:36.996Z
Learning: Repo: dashpay/docs — When examples show dash-cli command output, keep them verbatim (do not remove or tweak fields for clarity), even if multiple versions of a field (e.g., "next" and "next_index") appear. Applies across API docs, including docs/core/api/remote-procedure-calls-wallet.md.
Learnt from: thephez
Repo: dashpay/docs PR: 525
File: docs/core/api/remote-procedure-call-quick-reference.md:34-34
Timestamp: 2025-11-10T17:22:58.160Z
Learning: In the dashpay/docs repository, RPC documentation descriptions in files like `docs/core/api/remote-procedure-call-quick-reference.md` are derived from the Dash Core application help output. These descriptions should not be modified for grammar or style, as they need to remain consistent with the source application output.
📚 Learning: 2025-11-10T17:22:58.160Z
Learnt from: thephez
Repo: dashpay/docs PR: 525
File: docs/core/api/remote-procedure-call-quick-reference.md:34-34
Timestamp: 2025-11-10T17:22:58.160Z
Learning: In the dashpay/docs repository, RPC documentation descriptions in files like `docs/core/api/remote-procedure-call-quick-reference.md` are derived from the Dash Core application help output. These descriptions should not be modified for grammar or style, as they need to remain consistent with the source application output.
Applied to files:
locale/ar/LC_MESSAGES/docs/user/introduction/information.polocale/en/LC_MESSAGES/docs/user/developers/insight.polocale/de/LC_MESSAGES/docs/user/wallets/dashcore/installation-windows.polocale/ar/LC_MESSAGES/docs/user/network/dashmate/index.polocale/el/LC_MESSAGES/docs/user/masternodes/hosting.polocale/ar/LC_MESSAGES/docs/user/introduction/about.polocale/el/LC_MESSAGES/docs/user/network/dashmate/index.polocale/es/LC_MESSAGES/docs/user/masternodes/setup-evonode.polocale/de/LC_MESSAGES/docs/user/developers/insight.polocale/de/LC_MESSAGES/docs/user/earning-spending.polocale/ar/LC_MESSAGES/docs/user/wallets/dashcore/installation-windows.polocale/el/LC_MESSAGES/docs/user/developers/insight.polocale/es/LC_MESSAGES/docs/user/developers/insight.polocale/es/LC_MESSAGES/docs/user/introduction/information.polocale/en/LC_MESSAGES/docs/user/earning-spending.polocale/de/LC_MESSAGES/docs/user/introduction/about.polocale/ar/LC_MESSAGES/docs/user/developers/insight.polocale/de/LC_MESSAGES/docs/user/introduction/information.polocale/fr/LC_MESSAGES/docs/user/introduction/about.polocale/en/LC_MESSAGES/docs/user/introduction/about.polocale/de/LC_MESSAGES/docs/user/masternodes/setup-evonode.polocale/en/LC_MESSAGES/docs/user/wallets/dashcore/installation-windows.polocale/es/LC_MESSAGES/docs/user/masternodes/hosting.polocale/el/LC_MESSAGES/docs/user/introduction/about.polocale/el/LC_MESSAGES/docs/user/masternodes/setup-evonode.polocale/es/LC_MESSAGES/docs/user/introduction/about.polocale/de/LC_MESSAGES/docs/user/wallets/dashcore/installation-linux.polocale/ar/LC_MESSAGES/docs/user/wallets/dashcore/installation-linux.polocale/en/LC_MESSAGES/docs/user/introduction/information.polocale/ar/LC_MESSAGES/docs/user/earning-spending.polocale/de/LC_MESSAGES/docs/user/network/dash-evo-tool/index.polocale/el/LC_MESSAGES/docs/user/wallets/dashcore/installation-linux.polocale/es/LC_MESSAGES/docs/user/wallets/dashcore/installation-linux.polocale/el/LC_MESSAGES/docs/user/earning-spending.polocale/el/LC_MESSAGES/docs/user/introduction/information.polocale/en/LC_MESSAGES/docs/user/wallets/dashcore/installation-linux.po
📚 Learning: 2025-11-10T18:51:36.996Z
Learnt from: thephez
Repo: dashpay/docs PR: 525
File: docs/core/api/remote-procedure-calls-wallet.md:1737-1738
Timestamp: 2025-11-10T18:51:36.996Z
Learning: Repo: dashpay/docs — When examples show dash-cli command output, keep them verbatim (do not remove or tweak fields for clarity), even if multiple versions of a field (e.g., "next" and "next_index") appear. Applies across API docs, including docs/core/api/remote-procedure-calls-wallet.md.
Applied to files:
locale/ar/LC_MESSAGES/docs/user/introduction/information.polocale/en/LC_MESSAGES/docs/user/developers/insight.polocale/de/LC_MESSAGES/docs/user/wallets/dashcore/installation-windows.polocale/ar/LC_MESSAGES/docs/user/network/dashmate/index.polocale/ar/LC_MESSAGES/docs/user/introduction/about.polocale/es/LC_MESSAGES/docs/user/masternodes/setup-evonode.polocale/de/LC_MESSAGES/docs/user/developers/insight.polocale/de/LC_MESSAGES/docs/user/earning-spending.polocale/ar/LC_MESSAGES/docs/user/wallets/dashcore/installation-windows.polocale/el/LC_MESSAGES/docs/user/developers/insight.polocale/es/LC_MESSAGES/docs/user/developers/insight.polocale/es/LC_MESSAGES/docs/user/introduction/information.polocale/en/LC_MESSAGES/docs/user/earning-spending.polocale/de/LC_MESSAGES/docs/user/introduction/about.polocale/ar/LC_MESSAGES/docs/user/developers/insight.polocale/de/LC_MESSAGES/docs/user/introduction/information.polocale/fr/LC_MESSAGES/docs/user/introduction/about.polocale/ar/LC_MESSAGES/docs/user/network/dash-evo-tool/index.polocale/en/LC_MESSAGES/docs/user/wallets/dashcore/installation-windows.polocale/el/LC_MESSAGES/docs/user/introduction/about.polocale/en/LC_MESSAGES/docs/user/wallets/hardware.polocale/es/LC_MESSAGES/docs/user/introduction/about.polocale/el/LC_MESSAGES/docs/user/wallets/dashcore/installation-windows.polocale/de/LC_MESSAGES/docs/user/wallets/dashcore/installation-linux.polocale/ar/LC_MESSAGES/docs/user/wallets/dashcore/installation-linux.polocale/fr/LC_MESSAGES/docs/user/earning-spending.polocale/en/LC_MESSAGES/docs/user/introduction/information.polocale/es/LC_MESSAGES/docs/user/earning-spending.polocale/ar/LC_MESSAGES/docs/user/earning-spending.polocale/en/LC_MESSAGES/docs/user/network/dash-evo-tool/index.polocale/de/LC_MESSAGES/docs/user/network/dash-evo-tool/index.polocale/el/LC_MESSAGES/docs/user/network/dash-evo-tool/index.polocale/es/LC_MESSAGES/docs/user/network/dash-evo-tool/index.polocale/el/LC_MESSAGES/docs/user/wallets/dashcore/installation-linux.polocale/es/LC_MESSAGES/docs/user/wallets/dashcore/installation-linux.polocale/el/LC_MESSAGES/docs/user/earning-spending.polocale/el/LC_MESSAGES/docs/user/introduction/information.polocale/en/LC_MESSAGES/docs/user/wallets/dashcore/installation-linux.po
📚 Learning: 2025-11-10T19:11:33.313Z
Learnt from: thephez
Repo: dashpay/docs PR: 525
File: docs/core/api/remote-procedure-calls-wallet.md:1702-1704
Timestamp: 2025-11-10T19:11:33.313Z
Learning: Repo: dashpay/docs — For ListDescriptors RPC, document Parameter #1 `private` (bool, default false) and note that `mnemonic` and `mnemonicpassphrase` appear only when `private=true` and the wallet was created with a mnemonic. Both fields are strings per Dash Core v23.0 help (scripts/core-rpc-tools/dash-cli-help-23.0.0.jsonl).
Applied to files:
locale/ar/LC_MESSAGES/docs/user/introduction/information.polocale/ar/LC_MESSAGES/docs/user/introduction/about.polocale/es/LC_MESSAGES/docs/user/introduction/information.polocale/de/LC_MESSAGES/docs/user/introduction/about.polocale/de/LC_MESSAGES/docs/user/introduction/information.polocale/fr/LC_MESSAGES/docs/user/introduction/about.polocale/el/LC_MESSAGES/docs/user/introduction/about.polocale/es/LC_MESSAGES/docs/user/introduction/about.polocale/de/LC_MESSAGES/docs/user/wallets/dashcore/installation-linux.polocale/ar/LC_MESSAGES/docs/user/wallets/dashcore/installation-linux.polocale/en/LC_MESSAGES/docs/user/introduction/information.polocale/el/LC_MESSAGES/docs/user/wallets/dashcore/installation-linux.polocale/es/LC_MESSAGES/docs/user/wallets/dashcore/installation-linux.polocale/el/LC_MESSAGES/docs/user/introduction/information.polocale/en/LC_MESSAGES/docs/user/wallets/dashcore/installation-linux.po
🔇 Additional comments (80)
locale/ar/LC_MESSAGES/docs/user/introduction/information.po (1)
1-2573: LGTM - Routine translation update.This Arabic translation file has been properly updated with the latest POT-Creation-Date (2025-11-11) and line reference adjustments. The changes are consistent with automated Transifex synchronization, including metadata updates, line number realignments, and translation refinements.
Note: Arabic translation content quality cannot be validated without language expertise, but the file structure and metadata are correct.
locale/ar/LC_MESSAGES/docs/user/introduction/about.po (1)
1-209: LGTM - Routine translation update.This Arabic translation file has been properly updated with the latest metadata (POT-Creation-Date: 2025-11-11), corrected FIRST AUTHOR year, and appropriate format markers (
#, python-format). The source reference adjustments and content refinements are consistent with automated Transifex synchronization.Note: Arabic translation content quality cannot be validated without language expertise, but the file structure, metadata, and format markers are correct.
locale/de/LC_MESSAGES/docs/user/introduction/about.po (1)
1-216: LGTM – Routine translation file update from Transifex.This is a machine-generated German translation file updated via the Transifex sync script. The changes consist of standard metadata updates (POT-Creation-Date, Generated-By Babel 2.16.0), source reference format adjustments, and text reflow—all typical of automated translation management tooling. No issues identified.
locale/ar/LC_MESSAGES/docs/user/network/dash-evo-tool/index.po (1)
13-13: LGTM! Translation file properly updated.The changes correctly update the POT-Creation-Date and consistently bump all download URLs from v0.9.0 to v0.9.3 across all five platforms (Windows, Mac ARM/x86, Linux x86/ARM). The obsolete entries are appropriately preserved with the
#~prefix per standard PO file conventions.Also applies to: 65-90, 1659-1687
locale/de/LC_MESSAGES/docs/user/wallets/hardware.po (1)
1-719: LGTM! Translation file update is correctly formatted.This is a standard automated update from the Transifex translation management system. The changes include:
- POT-Creation-Date metadata updated to reflect the latest documentation snapshot
- Line reference adjustments to align with source documentation changes
- Obsolete entries properly marked with
#~prefix for removed review linksThe file follows correct gettext .po format conventions, and all structural changes are appropriate for a translation synchronization update.
locale/es/LC_MESSAGES/docs/user/wallets/hardware.po (1)
16-16: LGTM! Standard translation file update.The changes are appropriate for a Transifex-generated translation update:
- POT-Creation-Date timestamp updated to reflect the current sync
- Line reference adjustments track source RST file modifications
- Obsolete entries properly marked for removed review links
- All Spanish translations remain intact
Also applies to: 76-720
locale/el/LC_MESSAGES/docs/user/wallets/hardware.po (1)
11-11: LGTM! Standard translation file update.The changes are appropriate for a Transifex-generated translation update:
- POT-Creation-Date timestamp updated consistently with other locales
- Line reference adjustments track source RST file modifications
- Obsolete entries properly marked for removed review links
- Untranslated entries remain properly formatted for future translation work
Also applies to: 65-596
locale/ar/LC_MESSAGES/docs/user/earning-spending.po (1)
1-403: LGTM! Automated translation update is properly formatted.This is a routine translation file update generated by the Transifex automation script. The file format is correct, metadata has been appropriately updated, and the structure follows PO file standards. Empty
msgstrvalues for new or modified content are expected and will be filled by translators through the Transifex platform.locale/en/LC_MESSAGES/docs/user/wallets/hardware.po (3)
11-11: LGTM: Metadata update is correct.The POT-Creation-Date has been properly updated to reflect the current translation sync run.
63-369: LGTM: Line reference updates are consistent.The updated line number references correctly reflect changes in the source RST file structure. These automated updates maintain proper mapping between translation strings and their source locations.
593-597: LGTM: Obsolete entries are properly marked.The removed review links are correctly marked as obsolete with the
#~prefix, following PO file conventions for maintaining translation history.locale/es/LC_MESSAGES/docs/user/introduction/information.po (2)
18-18: LGTM! Translation file metadata properly updated.The POT-Creation-Date has been correctly updated to reflect the November 2025 translation refresh from Transifex. The timezone adjustment from -0400 to -0500 is expected due to daylight saving time differences between July and November.
1-2713: Translation file structure verified - automated Transifex update is correct.This Spanish translation file has been properly updated through the Transifex translation management system. The changes consist of:
- Updated POT-Creation-Date metadata (November 11, 2025)
- Realigned source file line number references throughout
- Maintained valid GNU gettext PO file format
The file structure is intact, all message pairs are properly formatted, and no syntax errors are present. This is a standard automated translation update.
locale/fr/LC_MESSAGES/docs/user/earning-spending.po (4)
14-14: LGTM! Metadata update reflects template regeneration.The POT-Creation-Date update to November 11, 2025 correctly reflects the new translation template generation date from the Transifex script execution.
81-90: Source text updated; translations pending through Transifex.The msgid entries have been updated with new URL formatting for Bitwage and Uphold links. The empty msgstr entries indicate translations will be provided by translators through the Transifex platform.
101-138: Fuzzy translations flagged for translator review.The
#, fuzzymarkers on lines 102 and 123 correctly indicate that source text has changed and existing translations need review. This is standard PO file behavior and will be addressed by translators through the Transifex workflow.
1-477: File structure is valid and follows PO format conventions.The translation file is properly formatted with:
- Valid PO file syntax throughout
- Obsolete entries correctly marked with
#~prefix for historical reference- Proper metadata headers
- Appropriate line reference annotations
This is a routine translation file update from the Transifex automation.
locale/ar/LC_MESSAGES/docs/user/wallets/hardware.po (3)
14-14: LGTM! POT-Creation-Date correctly updated.The POT-Creation-Date timestamp has been properly updated to reflect the latest translation template generation on 2025-11-11, which aligns with the PR creation date.
72-438: LGTM! Line number references correctly updated.The line number references in the msgid context comments have been properly updated to match changes in the source documentation file (
docs/user/wallets/hardware.rst). This is standard behavior when the translation template is regenerated after source documentation updates. The actual translation content (msgstr values) remains intact.
669-673: LGTM! Obsolete entries properly formatted.The obsolete entries for the Ledger Nano S and Trezor hardware wallet review links are correctly formatted with the
#~prefix, indicating these references have been removed from the source documentation. This is standard practice in.pofiles to maintain translation history.locale/en/LC_MESSAGES/docs/user/masternodes/hosting.po (1)
11-11: LGTM! Routine translation file maintenance.The updates correctly reflect:
- Updated POT creation date metadata
- NodeHub.io pricing change ($4.80→$3.90/month)
- Social link updates (Twitter→X, Discord URL)
- Proper preservation of obsolete entries for translation history
These changes are consistent with automated translation management system updates.
Also applies to: 248-248, 266-266, 274-274, 519-526
locale/es/LC_MESSAGES/docs/user/masternodes/hosting.po (1)
15-15: LGTM! Spanish translation updates are consistent.The updates mirror the English source changes appropriately. The fuzzy marker on the X (Twitter) link (lines 285-287) correctly flags the entry for translator review, which is expected when source content changes.
Also applies to: 267-267, 285-287, 294-294, 453-460
locale/el/LC_MESSAGES/docs/user/masternodes/hosting.po (1)
11-11: LGTM! Greek locale file properly updated.Metadata and source strings updated consistently with the English base file. Empty translations are expected for an untranslated locale.
Also applies to: 250-250, 268-268, 276-276, 429-436
locale/de/LC_MESSAGES/docs/user/masternodes/hosting.po (1)
13-13: LGTM! German translation file updates are correct.All factual updates (pricing, URLs, metadata) are consistent with the source changes. Existing German translations properly preserved.
Also applies to: 262-262, 280-280, 288-288, 441-448
locale/ar/LC_MESSAGES/docs/user/masternodes/hosting.po (1)
13-13: LGTM! Arabic translation file updates are consistent.All changes align with the other locale files. Fuzzy markers appropriately flag the updated social links for Arabic translator review. Arabic plural forms metadata is correctly configured.
Also applies to: 260-260, 278-280, 287-289, 443-450
locale/en/LC_MESSAGES/docs/user/introduction/about.po (3)
11-11: LGTM: Standard metadata updates.The POT-Creation-Date and Generated-By updates reflect the automated translation synchronization process and Babel version in use.
Also applies to: 18-18
177-181: LGTM: Proper obsolete entry handling.The obsolete block correctly preserves the previous URL string with the
#~marker, which is standard gettext behavior for tracking changed source strings.
145-146: URL migration verified successfully.The new URL at
media.dash.orgis accessible and serves the correct PDF content (HTTP 200, valid application/pdf). The old URL returns a redirect (HTTP 302), confirming this was an intentional infrastructure migration. The change is valid and requires no action.locale/el/LC_MESSAGES/docs/user/introduction/information.po (2)
13-13: LGTM! Metadata timestamp updated appropriately.The POT-Creation-Date has been correctly updated to reflect the November 2025 sync from Transifex. This is standard for translation file maintenance.
89-94: Cross-reference and line number updates look correct.The line number adjustments throughout the file reflect changes in the source documentation structure. These mechanical updates from the Transifex sync ensure translation entries remain aligned with the current source files.
Note: The empty
msgstrvalues and#, fuzzyflag (line 8) indicate this Greek locale has incomplete translations, which is expected and normal for translation workflows managed through Transifex.Also applies to: 326-2123
locale/es/LC_MESSAGES/docs/user/introduction/about.po (2)
1-26: Routine translation file maintenance looks good.The metadata updates (POT-Creation-Date, Babel version, language headers), reference anchor changes (to
-1), text reflow, and obsolete entry additions are all standard for automated Transifex synchronization. The PO file format is correct and the changes maintain translation integrity.Also applies to: 27-38, 39-209
184-190: Thepython-formatflag is a systematic pattern, not a code issue.The
#, python-formatflag appears across multiple locale files (zh_CN, es, etc.) for the same InstantSend whitepaper entry and other entries with%characters. This is a systematic pattern where the translation tooling (Sphinx gettext/Babel) marks any string containing%as python-format, regardless of whether it contains actual Python format specifiers (%s,%d, etc.) or just URL-encoded characters (%20) or percentage symbols (35%).While technically the flag is incorrect for URL-encoded strings, this is a pre-existing artifact of the translation pipeline, not an error in this PR. The flag has no runtime impact on PO files and doesn't affect functionality.
locale/fr/LC_MESSAGES/docs/user/introduction/about.po (3)
17-24: LGTM! Metadata normalization improves localization support.The additions of the
Languagefield,Plural-Forms, and the charset update to UTF-8 are all positive improvements that enhance proper localization handling.
43-255: LGTM! Translation updates properly reflect the updated English source.The French translations have been appropriately updated to match the revised English content, maintaining proper grammar and fluency. The addition of the
python-formatmarker on line 231 is correct for the InstantSend whitepaper entry containing format placeholders.
4-4: The year was not changed from 2023 to 2022. According to git history, the previous value was the placeholderYEAR, which has now been set to2022by the Transifex update script. This is standard behavior for .po file updates and represents forward progress, not a regression.Likely an incorrect or invalid review comment.
locale/de/LC_MESSAGES/docs/user/wallets/dashcore/installation-linux.po (1)
14-14: LGTM! Routine translation file update.The automated Transifex update correctly reflects the Dash Core version bump to 23.0.0, adds new documentation sections for library requirements, updates line references to match the source RST file, and properly marks obsolete entries for older versions.
Also applies to: 158-161, 163-177, 371-377
locale/el/LC_MESSAGES/docs/user/wallets/dashcore/installation-linux.po (1)
11-11: LGTM! Routine translation file update.The automated Transifex update correctly reflects the Dash Core version bump to 23.0.0, adds new documentation sections for library requirements, updates line references to match the source RST file, and properly marks obsolete entries. Empty translations are expected and will be populated through the Transifex translation workflow.
Also applies to: 147-150, 152-166, 351-357
locale/ar/LC_MESSAGES/docs/user/masternodes/setup-evonode.po (2)
13-13: POT-Creation-Date bump looks good.
372-375: Dashmate 2.1.3 consistency verified across all active locales. All active msgid entries in locale files (across 15+ locales) referencedashmate_2.1.3.077ec826f-1_amd64.debconsistently. Older versions (1.8.0, 2.0.1) appear only in archived/commented entries (marked#~).locale/el/LC_MESSAGES/docs/user/masternodes/setup.po (1)
11-11: POT-Creation-Date bump looks good.locale/de/LC_MESSAGES/docs/user/masternodes/setup-evonode.po (2)
11-11: POT-Creation-Date bump looks good.
362-364: Updated dashmate .deb path (2.1.3) — OK.locale/es/LC_MESSAGES/docs/user/masternodes/setup-evonode.po (2)
15-15: POT-Creation-Date bump looks good.
382-385: Updated dashmate .deb path (2.1.3) — OK.locale/es/LC_MESSAGES/docs/user/masternodes/setup.po (2)
16-16: POT-Creation-Date bump looks good.
793-795: Field rename tocoreP2PAddrs— OK.
Keep the code identifier unlocalized.locale/el/LC_MESSAGES/docs/user/masternodes/setup-testnet.po (2)
11-11: POT-Creation-Date bump looks good.
650-652: Field rename tocoreP2PAddrsverified and complete.Verification confirms that
coreP2PAddrsinsetup-testnet.pocorrectly corresponds to theprotx register_preparecommand (setup-testnet.rst line 491), whileipAndPortinmaintenance.pocorrectly remains for theprotx update_servicecommands (maintenance.rst lines 118, 151). These are distinct parameters in different operational contexts—the rename is properly scoped and consistent across all locale files.locale/en/LC_MESSAGES/docs/user/masternodes/setup.po (2)
11-11: POT-Creation-Date bump looks good.
721-723: Field rename tocoreP2PAddrs— OK.
Matches current parameter name; backticks preserved.locale/ar/LC_MESSAGES/docs/user/masternodes/setup-testnet.po (2)
13-13: POT-Creation-Date bump looks good.
665-667: Field rename tocoreP2PAddrs— OK.
Keep identifiers in backticks untranslated.locale/el/LC_MESSAGES/docs/user/masternodes/setup-evonode.po (3)
11-11: POT date bump looks good.
Header timestamp and timezone updated as expected.
951-957: Obsolete entry retained for history.
Keeping the prior 2.0.1 example under #~ is appropriate.
361-364: dashmate .deb version update verified as consistent across all locales.Verification confirms 2.1.3 is active across all locale files, with older versions (1.8.0, 2.0.1) properly in obsolete (#~) blocks. The file at lines 361–364 shows the correct updated version. No mixed versions linger in active strings.
locale/en/LC_MESSAGES/docs/user/masternodes/setup-evonode.po (2)
11-11: POT date bump OK.
Matches the update across locales.
359-364: dashmate .deb path updated to 2.1.3…
Looks consistent with the evonode install note. Confirm no active strings still reference 2.0.x outside #~.Use the script posted in the Greek file comment to scan the repo.
locale/ar/LC_MESSAGES/docs/user/masternodes/setup.po (2)
14-14: POT date bump OK.
No issues.
763-765: ipAndPort → coreP2PAddrs migration acknowledged.
The new parameter text reflects an array; ensure all setup*.po files use this new key only in active entries.Run the repo audit script (posted in the Greek file comment) to confirm no active ipAndPort remains.
locale/de/LC_MESSAGES/docs/user/masternodes/setup.po (2)
11-11: POT date bump OK.
723-725: Parameter rename to coreP2PAddrs looks correct.
Please verify there’s no active ipAndPort left outside #~.Use the repo audit script shared earlier.
locale/es/LC_MESSAGES/docs/user/masternodes/setup-testnet.po (2)
15-15: POT date bump OK.
681-683: coreP2PAddrs update aligned with other locales.
Good. Recommend running the repo audit to ensure consistency.Use the shared script to confirm no active ipAndPort remains.
locale/de/LC_MESSAGES/docs/user/masternodes/setup-testnet.po (2)
11-11: POT date bump OK.
650-652: coreP2PAddrs term adopted.
Looks good; ensure no active ipAndPort persists.Run the previously provided repo audit script.
locale/en/LC_MESSAGES/docs/user/masternodes/setup-testnet.po (2)
11-11: POT date bump OK.
648-650: coreP2PAddrs migration acknowledged.
Matches other locales and testnet context.locale/el/LC_MESSAGES/docs/user/introduction/about.po (1)
155-160: No duplicate msgids found; review comment is incorrect.The PO file structure is correct. What the review comment flagged as "duplicates" are actually msgstr (translation) blocks following their corresponding msgid blocks. This is standard PO format:
- Lines 154-160: One entry with msgid at 154 and msgstr at 157
- Lines 163-169: One entry with msgid at 163 and msgstr at 166
Each entry has exactly one msgid and one msgstr. The file contains no actual duplicate msgids.
Likely an incorrect or invalid review comment.
locale/el/LC_MESSAGES/docs/user/earning-spending.po (1)
14-14: LGTM! Routine translation catalog update.The POT-Creation-Date metadata and content updates are consistent with the automated Transifex synchronization. The updated English source strings now use proper inline code markup and consolidated sections, with corresponding Greek translation updates.
Also applies to: 79-114
locale/es/LC_MESSAGES/docs/user/developers/insight.po (1)
14-14: LGTM! Dash Core version reference updated.The POT-Creation-Date metadata and exec path have been correctly updated from dashcore-22.1.3 to dashcore-23.0.0, with the obsolete entry properly preserved.
Also applies to: 92-92, 125-126
locale/fr/LC_MESSAGES/docs/user/developers/insight.po (1)
13-13: LGTM! Version reference updated.The POT-Creation-Date and exec path have been updated to reference dashcore-23.0.0. The fuzzy flag is appropriate for indicating the translation may need review by French translators.
Also applies to: 95-97
locale/de/LC_MESSAGES/docs/user/developers/insight.po (1)
13-13: LGTM! Version update applied consistently.The POT-Creation-Date and exec path reference have been properly updated to dashcore-23.0.0, with the obsolete entry preserving the historical reference.
Also applies to: 90-90, 123-124
locale/ar/LC_MESSAGES/docs/user/network/dashmate/index.po (1)
13-13: LGTM! Dashmate package version updated.The POT-Creation-Date and dashmate package reference have been correctly updated from version 2.0.1.5f93c7072-1 to 2.1.3.077ec826f-1, with the obsolete entry properly preserved.
Also applies to: 104-104, 948-954
locale/el/LC_MESSAGES/docs/user/network/dashmate/index.po (1)
13-13: LGTM! Dashmate version reference updated.The POT-Creation-Date and dashmate Debian package path have been properly updated to version 2.1.3.077ec826f-1, with the obsolete entry preserving the historical reference.
Also applies to: 103-103, 947-953
locale/ar/LC_MESSAGES/docs/user/developers/insight.po (1)
11-11: LGTM! Dash Core version updated.The POT-Creation-Date and exec path reference have been correctly updated to dashcore-23.0.0, with the obsolete entry properly preserved.
Also applies to: 84-84, 115-116
locale/el/LC_MESSAGES/docs/user/developers/insight.po (1)
11-11: LGTM! Version reference updated consistently.The POT-Creation-Date and exec path have been properly updated to dashcore-23.0.0, with the obsolete entry preserving the historical reference. All translation files in this PR show consistent, automated updates from the Transifex synchronization.
Also applies to: 83-83, 114-115
locale/de/LC_MESSAGES/docs/user/network/dashmate/index.po (1)
13-13: Dashmate release details look correct.Timestamp and
.debfilename both line up with the 2.1.3 drop; no issues spotted.Also applies to: 101-104
locale/en/LC_MESSAGES/docs/user/developers/insight.po (1)
11-11: Dash Core path bump confirmed.New POT date and the
dashcore-23.0.0exec reference are consistent with the version uplift.Also applies to: 58-58
locale/es/LC_MESSAGES/docs/user/network/dashmate/index.po (1)
14-14: Spanish locale matches the dashmate 2.1.3 update.Both metadata and the quoted
.debpath are in sync with the new release.Also applies to: 103-106
locale/en/LC_MESSAGES/docs/user/network/dashmate/index.po (1)
11-11: English locale metadata + package reference are on point.The updated POT date and dashmate
.debname align with the 2.1.3 build.Also applies to: 101-104
|
Close in favor of #534 |
1 participant
Based on running the transifex/pushtx.sh script
Summary by CodeRabbit
Release Notes