WEB-771 feat: sync 70+ remittance translation keys across all locales#3201
Merged
IOhacker merged 1 commit intoopenMF:devfrom Feb 22, 2026
Merged
Conversation
|
Note
|
| Cohort / File(s) | Summary |
|---|---|
Bulk translation updates src/assets/translations/cs-CS.json, src/assets/translations/de-DE.json, src/assets/translations/es-CL.json, src/assets/translations/fr-FR.json, src/assets/translations/it-IT.json, src/assets/translations/ko-KO.json, src/assets/translations/lt-LT.json, src/assets/translations/lv-LV.json, src/assets/translations/ne-NE.json, src/assets/translations/pt-PT.json, src/assets/translations/sw-SW.json |
Added ~80–90 remittance/payout-related keys per file: new button/label strings (Assign Payout, Confirm Payment, New Remittance, Print Receipt, Validate Recipient, View Receipt, Add Entry, Retry, Process Remittance), and expanded catalogs, inputs, placeholders, status, auditTrail, dialogs, validation/error messages, and vendor/recipient field labels. Pattern consistent across locales. |
Small translation update src/assets/translations/es-MX.json |
Added labels.buttons.Remittances ("Remesas"), menus.Remittances ("Remesas"), texts.Process Remittance ("Procesar Remesa"); adjusted labels.buttons.UploadDocumentHint punctuation. |
Estimated code review effort
🎯 2 (Simple) | ⏱️ ~15 minutes
Possibly related PRs
- WEB-673 Create a tasks sections just like it was available in the legacy mifos community app #3106 — Modifies the same translation JSON keys/namespaces (Advanced Search / Pending Tasks / translations) across locale files.
- WEB-596:feat(clients) add Personal Data tab with comprehensive client… #3006 — Overlaps edits to translation resources (e.g.,
cs-CS.json) and introduces related localization keys.
Suggested reviewers
- IOhacker
- alberto-art3ch
🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
| Check name | Status | Explanation |
|---|---|---|
| Description Check | ✅ Passed | Check skipped - CodeRabbit’s high-level summary is enabled. |
| Title check | ✅ Passed | The title accurately describes the main change: adding 70+ remittance translation keys across all non-English locales to address missing translations in the remittance workflow UI. |
| Docstring Coverage | ✅ Passed | No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. |
✏️ Tip: You can configure your own custom pre-merge checks in the settings.
✨ Finishing Touches
🧪 Generate unit tests (beta)
- Create PR with unit tests
- Post copyable unit tests in a comment
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 help to get the list of available commands and usage tips.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 4
Note
Due to the large number of review comments, Critical, Major severity comments were prioritized as inline comments.
🟡 Minor comments (39)
src/assets/translations/es-CL.json-564-571 (1)
564-571:⚠️ Potential issue | 🟡 MinorUntranslated English strings in es-CL remittance UI
New keys for remittance/payout remain in English, which will render untranslated UI for Chilean Spanish users. Please translate these values (or align with es-MX/es-ES if that’s the project convention).
Also applies to: 1308-1331, 2716-2735, 2880-2885, 2871-2873, 3614-3630, 3927-3928
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/es-CL.json` around lines 564 - 571, Several remittance/payout UI strings are still in English; update the JSON values for the keys "Assign Payout", "Confirm Payment", "New Remittance", "Print Receipt", "Validate Recipient", "View Receipt", "Add Entry", and "Retry" to Chilean Spanish equivalents (or copy the established translations from es-MX/es-ES if project convention prefers). Locate these keys in src/assets/translations/es-CL.json (and the other ranges called out: 1308-1331, 2716-2735, 2880-2885, 2871-2873, 3614-3630, 3927-3928) and replace the English values with correct Spanish translations (e.g., "Assign Payout" → "Asignar Pago/Remesa" or the repo’s preferred phrasing) ensuring punctuation and capitalization match other entries.src/assets/translations/fr-FR.json-3928-3929 (1)
3928-3929:⚠️ Potential issue | 🟡 MinorStatus entry includes English string.
“Process Remittance” remains English in the status block. Please translate or confirm fallback intent.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/fr-FR.json` around lines 3928 - 3929, The "Process Remittance" status value in the translations file is still English; update the JSON entry for the key "Process Remittance" to a proper French translation (e.g., "Traitement des remises" or another approved localization) so it matches other status entries (see nearby "INACTIVE"), or explicitly confirm if leaving English is an intended fallback.src/assets/translations/fr-FR.json-2718-2737 (1)
2718-2737:⚠️ Potential issue | 🟡 MinorInput labels remain in English.
The new remittance-related input labels are in English (“Vendor”, “State”, “Municipality”, etc.). This will break locale consistency. Please translate to French or confirm English fallback is desired.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/fr-FR.json` around lines 2718 - 2737, Several new translation keys are still in English (e.g., "Vendor", "Vendor is required", "Voter ID", "National Identity Card Number", "State", "Municipality", "Locality", "New Locality", "Occupation", "Economic Activity", "Entity Member", "# Remittance", "Avg Amount/Transaction", "# Senders", "Sender Registry", "Individual", "Legal Entity", "External Reference ID"); update their French translations in the fr-FR.json entries so locale consistency is preserved (replace the English values with the appropriate French strings) or, if English fallback is intentional, add a short comment confirming that decision and leave values as-is. Ensure you update the value side of each quoted key listed above and keep JSON syntax intact.src/assets/translations/fr-FR.json-2881-2887 (1)
2881-2887:⚠️ Potential issue | 🟡 MinorPlaceholder text not localized.
New placeholders such as “Enter document number” and “Enter remittance reference number” are still English. Please translate or confirm intentional English usage.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/fr-FR.json` around lines 2881 - 2887, The JSON contains English placeholder values that must be localized; replace the values for the keys "Enter document number" and "Enter remittance reference number" with their French translations (e.g., "Entrez le numéro du document" and "Entrez le numéro de référence de remise") and scan nearby placeholder keys like "Enter first name (include middle name)" / "Enter last name" to ensure they are also translated consistently before committing.src/assets/translations/fr-FR.json-1311-1334 (1)
1311-1334:⚠️ Potential issue | 🟡 MinorNew “labels” entries are untranslated.
This block introduces many English values (e.g., “Beneficiary Details”, “Payment Receipt”, “Process Remittance”). Please provide French translations or document that English is intentionally used here.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/fr-FR.json` around lines 1311 - 1334, The new keys such as "Assign Payout", "Beneficiary Details", "Confirm Payment", "Payment Receipt", "Process Remittance", "Recipient Details", "Transaction Summary", "Transactional Profile", "Validated Recipient Information", "Payout Assignment", "Identification", "Professional Information", and "Add Profile Entry" are still in English; replace their values with proper French translations (e.g., translate "Beneficiary Details" to "Détails du bénéficiaire", "Payment Receipt" to "Reçu de paiement", "Process Remittance" to "Traiter le virement", etc.) or, if English is intentional, add a comment or document that these specific labels remain in English, ensuring consistency for keys like "Beneficiary Details" and "Payout Assignment" in the translations file.src/assets/translations/fr-FR.json-3614-3631 (1)
3614-3631:⚠️ Potential issue | 🟡 MinorUser-facing remittance messages are untranslated.
All newly added remittance messages are English and will appear in FR UI as-is. Please translate or confirm that English is acceptable for fr-FR.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/fr-FR.json` around lines 3614 - 3631, The listed remittance message values in src/assets/translations/fr-FR.json are still in English and must be translated to French; update the value strings for the keys "This remittance has a terminal status and cannot be processed further.", "This remittance has already been paid successfully.", "Review the transaction and recipient details below, then assign the payout.", "Please review the details carefully before confirming the payment.", "Register the transactional profile for the beneficiary. Add entries for individuals or legal entities.", "No transactional profile entries yet. Add one below.", "Click to remove", "Recipient is not valid for this transaction. Please check the details.", "Recipient validation failed. Please check the document details and try again.", "Missing required information. Please try again.", "Failed to confirm payment. Please try again or contact support.", "Failed to assign payout. Please try again.", "Remittance not found. Please check the reference number and try again.", "Unable to load vendors. Please check your connection and try again.", "Search and assign this beneficiary to an existing Mifos client account", "Failed to search clients. Please try again.", and "Process Remittance" with proper French translations (or confirm English is acceptable) keeping the keys unchanged and preserving punctuation/formatting.src/assets/translations/fr-FR.json-2873-2875 (1)
2873-2875:⚠️ Potential issue | 🟡 MinorMenu entries are in English.
“Remittances” and “Process Remittance” remain English under fr-FR. Please translate or confirm fallback strategy.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/fr-FR.json` around lines 2873 - 2875, The French translations for the keys "Remittances" and "Process Remittance" are still in English; update their values in fr-FR.json (the "Remittances" and "Process Remittance" entries) to proper French (e.g., "Remises" and "Traiter la remise" or your approved phrasing) or explicitly document/confirm the intended fallback strategy if leaving them untranslated, then run the localization build/tests to ensure the new strings appear in the UI.src/assets/translations/fr-FR.json-563-571 (1)
563-571:⚠️ Potential issue | 🟡 MinorLocalize new button labels to French.
Several new button values are still in English (e.g., “Assign Payout”, “Confirm Payment”, “New Remittance”). These will surface English in the FR UI. Please translate them or confirm that English is the intended fallback for fr-FR.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/fr-FR.json` around lines 563 - 571, The fr-FR translation file contains several English labels; update the values for the keys "Assign Payout", "Confirm Payment", "New Remittance", "Print Receipt", "Validate Recipient", "View Receipt", "Add Entry", and "Retry" in src/assets/translations/fr-FR.json to their French equivalents (for example: "Assign Payout" → "Attribuer le paiement", "Confirm Payment" → "Confirmer le paiement", "New Remittance" → "Nouvelle remise", "Print Receipt" → "Imprimer le reçu", "Validate Recipient" → "Valider le bénéficiaire", "View Receipt" → "Voir le reçu", "Add Entry" → "Ajouter une entrée", "Retry" → "Réessayer") unless English is intentionally required as the fallback. Ensure the replacement preserves JSON formatting and quotes for those keys.src/assets/translations/it-IT.json-2714-2733 (1)
2714-2733:⚠️ Potential issue | 🟡 MinorLocalize input labels, placeholders, and remittance messages.
These newly added values are still in English (inputs/placeholders/status/messages), which will present mixed-language UI for it-IT. Please translate them or confirm the intended fallback strategy.Also applies to: 2877-2883, 3612-3628, 3925-3926
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/it-IT.json` around lines 2714 - 2733, The listed translation keys (e.g., "Select entity", "Reference ID is required", "Vendor", "Vendor is required", "Voter ID", "National Identity Card Number", "State", "Municipality", "Locality", "New Locality", "Occupation", "Economic Activity", "Entity Member", "# Remittance", "Avg Amount/Transaction", "# Senders", "Sender Registry", "Individual", "Legal Entity", "External Reference ID") are still in English—update their values in src/assets/translations/it-IT.json to proper Italian equivalents (or explicitly set them to the intended fallback marker), and apply the same treatment for the other untranslated blocks noted (around the keys in ranges ~2877-2883, ~3612-3628, ~3925-3926) so the UI strings (labels/placeholders/status/remittance messages) are consistently localized.src/assets/translations/it-IT.json-1307-1330 (1)
1307-1330:⚠️ Potential issue | 🟡 MinorTranslate new headings and menu items.
The new remittance headings and menu entries are still in English. Please provide Italian translations for these keys to keep the UI consistent.Also applies to: 2869-2871
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/it-IT.json` around lines 1307 - 1330, Replace the English values for the listed translation keys with their Italian equivalents: update "Pending Tasks", "Assign Payout", "Assign to Mifos Client", "Beneficiary Details", "Confirm Payment", "Confirm Payout", "Confirmation Details", "Payment Receipt", "Payment Successful", "Process Remittance", "Recipient Details", "Remittance Details", "Search Beneficiary", "Search Remittance", "Transaction", "Transaction Status", "Transaction Summary", "Transactional Profile", "Validated Recipient Information", "Recipient", "Payout Assignment", "Identification", "Professional Information", and "Add Profile Entry" with proper Italian translations in the it-IT.json file, and make the same translations for the corresponding keys referenced at the other occurrence (lines 2869-2871) to ensure consistency across the UI.src/assets/translations/it-IT.json-562-570 (1)
562-570:⚠️ Potential issue | 🟡 MinorLocalize new button labels to Italian.
Lines 562-570 introduce English labels (e.g., “Assign Payout”, “Confirm Payment”). These should be translated to avoid mixed-language UI in it-IT.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/it-IT.json` around lines 562 - 570, Replace the English values for the listed keys with Italian translations so the it-IT locale is consistent: update "Assign Payout" -> "Assegna pagamento", "Confirm Payment" -> "Conferma pagamento", "New Remittance" -> "Nuova rimessa", "Print Receipt" -> "Stampa ricevuta", "Validate Recipient" -> "Valida destinatario", "View Receipt" -> "Visualizza ricevuta", "Add Entry" -> "Aggiungi voce", and "Retry" -> "Riprova" (keep "Hide advanced search" as-is since it's already localized); modify the JSON values for those exact keys in the it-IT translation file.src/assets/translations/lt-LT.json-3926-3927 (1)
3926-3927:⚠️ Potential issue | 🟡 MinorTranslate status label “Process Remittance”.
This entry is still English in the Lithuanian status block.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/lt-LT.json` around lines 3926 - 3927, The Lithuanian translation for the status label keyed as "Process Remittance" is still in English; update the value for the "Process Remittance" key in the lt-LT.json translations (near the "INACTIVE" entry) to the correct Lithuanian translation, e.g., "Apdoroti perlaidą" (or your approved Lithuanian phrase) so the status appears localized.src/assets/translations/lt-LT.json-2715-2734 (1)
2715-2734:⚠️ Potential issue | 🟡 MinorLocalize the new input labels/placeholders.
These input labels are still English in lt-LT and will render untranslated in the UI.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/lt-LT.json` around lines 2715 - 2734, The listed JSON keys (e.g., "Reference ID is required", "Vendor", "Vendor is required", "Voter ID", "National Identity Card Number", "State", "Municipality", "Locality", "New Locality", "Occupation", "Economic Activity", "Entity Member", "# Remittance", "Avg Amount/Transaction", "# Senders", "Sender Registry", "Individual", "Legal Entity", "External Reference ID") are still English in lt-LT.json; replace each value with the correct Lithuanian translation for those input labels/placeholders so the UI renders localized text (update the values only, preserving the keys and JSON structure). Ensure translations are idiomatic and consistent with existing terms used elsewhere in lt-LT.json.src/assets/translations/lt-LT.json-1306-1329 (1)
1306-1329:⚠️ Potential issue | 🟡 MinorLocalize the new “Pending Tasks” and remittance labels.
All added labels in this block are English; please provide Lithuanian translations (or confirm intentional fallback).🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/lt-LT.json` around lines 1306 - 1329, The JSON block adds several untranslated English keys (e.g., "Pending Tasks", "Assign Payout", "Assign to Mifos Client", "Beneficiary Details", "Confirm Payment", "Confirm Payout", "Confirmation Details", "Payment Receipt", "Payment Successful", "Process Remittance", "Recipient Details", "Remittance Details", "Search Beneficiary", "Search Remittance", "Transaction", "Transaction Status", "Transaction Summary", "Transactional Profile", "Validated Recipient Information", "Recipient", "Payout Assignment", "Identification", "Professional Information", "Add Profile Entry") in src/assets/translations/lt-LT.json; replace the English values with correct Lithuanian translations for each key (or explicitly mark them as intentional fallbacks if untranslated) so the locale file contains localized strings for those keys.src/assets/translations/lt-LT.json-2878-2884 (1)
2878-2884:⚠️ Potential issue | 🟡 MinorLocalize remittance placeholders.
These placeholders remain English; please translate for Lithuanian locale completeness.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/lt-LT.json` around lines 2878 - 2884, Several placeholder strings in lt-LT.json remain in English; update the translation values for the keys "# Remittance", "Enter document number", "Enter remittance reference number", "Sender name" (and any other English placeholders in the shown block) to their Lithuanian equivalents so the locale file is fully localized; edit the values in src/assets/translations/lt-LT.json replacing the English phrases with correct Lithuanian translations while preserving the same JSON keys.src/assets/translations/lt-LT.json-2870-2872 (1)
2870-2872:⚠️ Potential issue | 🟡 MinorTranslate new menu entries.
“Tasks”, “Remittances”, and “Process Remittance” are still English in the Lithuanian menu.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/lt-LT.json` around lines 2870 - 2872, Replace the English values for the Lithuanian translations of the "Remittances" and "Process Remittance" keys in lt-LT.json: change the value for "Remittances" from "Remittances" to "Perlaidos" (or "Pavedimai" if you prefer that terminology) and change "Process Remittance" from "Process Remittance" to "Apdoroti perlaidą" so the menu entries are fully translated (the key names "Remittances" and "Process Remittance" identify the entries to update; "Tasks" is already translated as "Užduotys").src/assets/translations/lt-LT.json-3612-3629 (1)
3612-3629:⚠️ Potential issue | 🟡 MinorLocalize new remittance helper/error text.
The new remittance workflow text is English; this will show untranslated strings in lt-LT.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/lt-LT.json` around lines 3612 - 3629, The lt-LT translation file contains new English strings that need Lithuanian translations—update the keys such as "UploadDocumentHint", "This remittance has a terminal status and cannot be processed further.", "This remittance has already been paid successfully.", "Review the transaction and recipient details below, then assign the payout.", "Please review the details carefully before confirming the payment.", "Register the transactional profile for the beneficiary. Add entries for individuals or legal entities.", "No transactional profile entries yet. Add one below.", "Click to remove", "Recipient is not valid for this transaction. Please check the details.", "Recipient validation failed. Please check the document details and try again.", "Missing required information. Please try again.", "Failed to confirm payment. Please try again or contact support.", "Failed to assign payout. Please try again.", "Remittance not found. Please check the reference number and try again.", "Unable to load vendors. Please check your connection and try again.", "Search and assign this beneficiary to an existing Mifos client account", "Failed to search clients. Please try again.", and "Process Remittance" with their correct Lithuanian translations in src/assets/translations/lt-LT.json so the remittance workflow is fully localized.src/assets/translations/lt-LT.json-563-571 (1)
563-571:⚠️ Potential issue | 🟡 MinorTranslate the new button labels for lt-LT.
These newly added button labels are still in English, which will surface English UI in the Lithuanian locale.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/lt-LT.json` around lines 563 - 571, Replace the English values for the listed translation keys with Lithuanian equivalents so the lt-LT locale shows Lithuanian UI: update "Assign Payout" → "Priskirti išmokėjimą", "Confirm Payment" → "Patvirtinti mokėjimą", "New Remittance" → "Naujas pervedimas", "Print Receipt" → "Atspausdinti kvitą", "Validate Recipient" → "Patvirtinti gavėją", "View Receipt" → "Peržiūrėti kvitą", "Add Entry" → "Pridėti įrašą", and "Retry" → "Bandyti iš naujo" in the JSON object (use the existing keys exactly as shown).src/assets/translations/pt-PT.json-563-571 (1)
563-571:⚠️ Potential issue | 🟡 MinorTranslate new remittance buttons for pt-PT.
These button labels are still in English (e.g., “Assign Payout”, “Confirm Payment”). Portuguese users will see English UI labels; please localize or confirm that English placeholders are acceptable.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/pt-PT.json` around lines 563 - 571, The PT-PT locale file contains untranslated button labels ("Assign Payout", "Confirm Payment", "New Remittance", "Print Receipt", "Validate Recipient", "View Receipt", "Add Entry", "Retry") so update src/assets/translations/pt-PT.json by replacing these English values with their Portuguese equivalents (e.g., "Assign Payout" -> "Atribuir Pagamento", "Confirm Payment" -> "Confirmar Pagamento", "New Remittance" -> "Nova Remessa", "Print Receipt" -> "Imprimir Recibo", "Validate Recipient" -> "Validar Destinatário", "View Receipt" -> "Ver Recibo", "Add Entry" -> "Adicionar Entrada", "Retry" -> "Tentar Novamente") ensuring the JSON keys remain unchanged and punctuation/quoting matches surrounding entries.src/assets/translations/pt-PT.json-2714-2733 (1)
2714-2733:⚠️ Potential issue | 🟡 MinorNew input labels remain English.
Several new inputs (e.g., “Reference ID is required”, “Vendor”, “Occupation”) are English-only. This will surface mixed-language forms in pt-PT.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/pt-PT.json` around lines 2714 - 2733, Several keys in the pt-PT translation JSON are left in English; update the values for the keys "Reference ID is required", "Vendor", "Vendor is required", "Voter ID", "National Identity Card Number", "State", "Municipality", "Locality", "New Locality", "Occupation", "Economic Activity", "Entity Member", "# Remittance", "Avg Amount/Transaction", "# Senders", "Sender Registry", "Individual", "Legal Entity", and "External Reference ID" to their correct Portuguese (pt-PT) equivalents (keeping the keys identical) so the UI displays consistent Portuguese labels and error messages.src/assets/translations/pt-PT.json-2877-2883 (1)
2877-2883:⚠️ Potential issue | 🟡 MinorRemittance placeholders are English.
New placeholders like “Enter document number” and “Enter remittance reference number” are untranslated. Recommend pt-PT translations for consistent UX.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/pt-PT.json` around lines 2877 - 2883, The entries for the keys "Enter document number", "Enter remittance reference number", and the "# Remittance" placeholder are still in English—update their values in src/assets/translations/pt-PT.json to Portuguese; for example, change "Enter document number" → "Introduza o número do documento", "Enter remittance reference number" → "Introduza o número de referência da remessa", and "# Remittance" → "# Remessa" (also review related keys like "Sender name" and "Enter first name (include middle name)" / "Enter last name" to ensure consistent pt-PT phrasing such as "Nome do remetente", "Introduza o primeiro nome (inclua o nome do meio)", "Introduza o último nome").src/assets/translations/pt-PT.json-2869-2871 (1)
2869-2871:⚠️ Potential issue | 🟡 MinorMenu entries should be localized.
“Remittances” and “Process Remittance” are English in the pt-PT menu section. Please translate or confirm placeholder policy.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/pt-PT.json` around lines 2869 - 2871, The pt-PT translation file contains English values for the keys "Remittances" and "Process Remittance" under the menu section; update those values to their Portuguese equivalents (e.g., "Remessas" and "Processar Remessa") or confirm and document a placeholder policy if intentionally left in English—edit the entries for "Remittances" and "Process Remittance" in src/assets/translations/pt-PT.json to reflect the chosen Portuguese translations or a clear placeholder comment.src/assets/translations/pt-PT.json-1307-1330 (1)
1307-1330:⚠️ Potential issue | 🟡 MinorLocalize the new remittance labels.
The added labels (e.g., “Payment Receipt”, “Transaction Summary”, “Recipient Details”) are in English inside the pt-PT file. Please translate or confirm the intended fallback behavior.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/pt-PT.json` around lines 1307 - 1330, Several new translation keys in the pt-PT locale (for example "Payment Receipt", "Payment Successful", "Process Remittance", "Recipient Details", "Remittance Details", "Transaction", "Transaction Status", "Transaction Summary", "Transactional Profile", "Validated Recipient Information", "Recipient", "Payout Assignment", "Identification", "Professional Information", "Add Profile Entry", "Assign Payout", "Assign to Mifos Client", "Beneficiary Details", "Confirm Payment", "Confirm Payout", "Confirmation Details", "Search Beneficiary", "Search Remittance", "Pending Tasks") are still in English; replace each value with the correct Portuguese (pt-PT) translation (or explicitly set an agreed fallback behavior) so the pt-PT resource is fully localized—edit the pt-PT JSON entries for those keys (e.g., "Payment Receipt": "...", "Transaction Summary": "...", "Recipient Details": "...") to the appropriate Portuguese strings.src/assets/translations/pt-PT.json-3611-3628 (1)
3611-3628:⚠️ Potential issue | 🟡 MinorUser-facing remittance messages need pt-PT translations.
The new remittance workflow messages are all English, so pt-PT users will see mixed language status and error text. Please translate or confirm the fallback approach.
Also applies to: 3925-3926
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/pt-PT.json` around lines 3611 - 3628, Several remittance-related i18n keys (e.g., "This remittance has a terminal status and cannot be processed further.", "This remittance has already been paid successfully.", "Review the transaction and recipient details below, then assign the payout.", "Please review the details carefully before confirming the payment.", "Failed to confirm payment. Please try again or contact support.", "Failed to assign payout. Please try again.", "Remittance not found. Please check the reference number and try again.", and "Process Remittance") are left in English in pt-PT JSON; replace each English value with the correct Portuguese (Portugal) translation (keeping the exact JSON keys unchanged) so users see full pt-PT text, and also apply the same translations for the related keys referenced at the other occurrence noted (lines 3925-3926) to ensure no mixed-language messages.src/assets/translations/sw-SW.json-563-571 (1)
563-571:⚠️ Potential issue | 🟡 MinorTranslate new remittance button labels for sw-SW.
Several newly added button labels are still in English, which will show a mixed-language UI in the Swahili locale. Please translate them or confirm the fallback policy for untranslated strings.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/sw-SW.json` around lines 563 - 571, The new Swahili translation file still contains English values for keys "Assign Payout", "Confirm Payment", "New Remittance", "Print Receipt", "Validate Recipient", "View Receipt", "Add Entry", and "Retry"; update sw-SW.json to provide proper Swahili translations for those keys (or, if your product policy prefers fallbacks, confirm and document that untranslated keys will fall back to English). Locate the entries for those exact keys in the JSON and replace the right-hand strings with the correct Swahili phrases (or add a comment/PR note stating the intentional fallback policy) so the sw-SW locale no longer mixes English UI text. Ensure JSON remains valid after edits.src/assets/translations/sw-SW.json-2875-2881 (1)
2875-2881:⚠️ Potential issue | 🟡 MinorPlaceholders are still English.
Remittance-related placeholders were added in English; these should be localized for sw-SW.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/sw-SW.json` around lines 2875 - 2881, The remittance-related placeholder strings in sw-SW.json are still in English; update the values for the keys "Enter document number", "Enter first name (include middle name)", "Enter last name", "Enter remittance reference number", "Sender name" (and the "# Remittance" label if intended for users) to their correct Swahili translations, preserving the exact JSON keys and punctuation/casing so the app picks up the localized placeholders (e.g., replace the English values with appropriate Swahili phrases).src/assets/translations/sw-SW.json-1305-1328 (1)
1305-1328:⚠️ Potential issue | 🟡 MinorSwahili locale labels remain in English.
The remittance workflow labels (e.g., beneficiary/transaction/payout items) are untranslated. Please provide Swahili translations or confirm that English is acceptable for this locale.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/sw-SW.json` around lines 1305 - 1328, The listed remittance UI labels (e.g., "Assign Payout", "Assign to Mifos Client", "Beneficiary Details", "Confirm Payment", "Confirm Payout", "Confirmation Details", "Payment Receipt", "Payment Successful", "Process Remittance", "Recipient Details", "Remittance Details", "Search Beneficiary", "Search Remittance", "Transaction", "Transaction Status", "Transaction Summary", "Transactional Profile", "Validated Recipient Information", "Recipient", "Payout Assignment", "Identification", "Professional Information", "Add Profile Entry") are still in English in src/assets/translations/sw-SW.json; update each value to the appropriate Swahili translation (or explicitly mark them as intentionally English) so the Swahili locale is complete—locate and edit the JSON keys listed above and replace their string values with the correct Swahili text or a comment/flag that English is intentional.src/assets/translations/sw-SW.json-3923-3924 (1)
3923-3924:⚠️ Potential issue | 🟡 MinorStatus label left in English.
“Process Remittance” under status remains English. Please localize for sw-SW.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/sw-SW.json` around lines 3923 - 3924, The JSON status label "Process Remittance" is still in English; replace its value with the Swahili translation (e.g., "Chakata Utoaji wa Malipo") so the key "Process Remittance" maps to the localized string, and ensure the surrounding JSON entry (near "INACTIVE": "HAITUMIKI") remains valid JSON and casing/format matches other translations.src/assets/translations/sw-SW.json-2867-2869 (1)
2867-2869:⚠️ Potential issue | 🟡 MinorMenu entries need localization.
The new menu items (“Tasks”, “Remittances”, “Process Remittance”) are English. Please translate for sw-SW to keep navigation consistent.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/sw-SW.json` around lines 2867 - 2869, The three menu entries are still in English; update the JSON values for the keys "Tasks", "Remittances", and "Process Remittance" to Swahili equivalents to localize navigation. Replace the value for "Tasks" (already "Kazi" — verify correctness), change "Remittances" to a Swahili term such as "Marejesho" (or "Marejesho ya Fedha" if you prefer more context), and change "Process Remittance" to something like "Chakata Marejesho" (or "Fanya Usindikaji wa Marejesho"); ensure the keys remain unchanged and the file remains valid JSON.src/assets/translations/sw-SW.json-3609-3626 (1)
3609-3626:⚠️ Potential issue | 🟡 MinorRemittance flow messages need Swahili translations.
User-facing remittance messages remain English, which breaks locale consistency. Please translate or confirm a deliberate fallback strategy.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/sw-SW.json` around lines 3609 - 3626, The JSON contains remittance message keys still in English (e.g., "This remittance has a terminal status and cannot be processed further.", "This remittance has already been paid successfully.", "Review the transaction and recipient details below, then assign the payout.", "Please review the details carefully before confirming the payment.", "Register the transactional profile for the beneficiary. Add entries for individuals or legal entities.", "No transactional profile entries yet. Add one below.", "Recipient is not valid for this transaction. Please check the details.", "Recipient validation failed. Please check the document details and try again.", "Missing required information. Please try again.", "Failed to confirm payment. Please try again or contact support.", "Failed to assign payout. Please try again.", "Remittance not found. Please check the reference number and try again.", "Unable to load vendors. Please check your connection and try again.", "Search and assign this beneficiary to an existing Mifos client account", "Failed to search clients. Please try again.", "Process Remittance") — translate each value into Swahili (or explicitly mark them to intentionally fallback to English) so the sw-SW locale is consistent; update the corresponding values in src/assets/translations/sw-SW.json for those exact keys and ensure translations preserve meaning and tone for UI/UX messages.src/assets/translations/sw-SW.json-2712-2731 (1)
2712-2731:⚠️ Potential issue | 🟡 MinorUntranslated remittance input/validation strings.
New input labels and validation messages are still in English. This will surface English text in sw-SW. Please translate or confirm the desired fallback behavior.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/sw-SW.json` around lines 2712 - 2731, Several keys in sw-SW JSON remain in English and must be translated into Swahili: update the values for "Select entity", "Reference ID is required", "Vendor", "Vendor is required", "Voter ID", "National Identity Card Number", "State", "Municipality", "Locality", "New Locality", "Occupation", "Economic Activity", "Entity Member", "# Remittance", "Avg Amount/Transaction", "# Senders", "Sender Registry", "Individual", "Legal Entity", and "External Reference ID" to their correct Swahili equivalents (e.g., "Select entity" -> "Chagua kiini/kifungu" or preferred localized term) keeping terminology consistent with the rest of sw-SW translations and matching pluralization/formatting conventions used elsewhere in the file; ensure validation messages like "Reference ID is required" and "Vendor is required" are translated as full sentences in Swahili and run a quick pass to fix the existing "Chagua huluki" typo to the chosen consistent term.src/assets/translations/de-DE.json-1308-1331 (1)
1308-1331:⚠️ Potential issue | 🟡 MinorLocalize the new remittance section labels.
The newly added labels (“Assign Payout”, “Assign to Mifos Client”, “Beneficiary Details”, “Confirm Payment”, “Process Remittance”, etc.) remain English in the German locale. This will appear untranslated in UI headings and summaries. Please provide German translations and keep terminology consistent with the button/menu labels.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/de-DE.json` around lines 1308 - 1331, Translate the new remittance keys in the de-DE JSON so they are German and consistent with existing terminology: replace values for "Assign Payout", "Assign to Mifos Client", "Beneficiary Details", "Confirm Payment", "Confirm Payout", "Confirmation Details", "Payment Receipt", "Payment Successful", "Process Remittance", "Recipient Details", "Remittance Details", "Search Beneficiary", "Search Remittance", "Transaction", "Transaction Status", "Transaction Summary", "Transactional Profile", "Validated Recipient Information", "Recipient", "Payout Assignment", "Identification", "Professional Information", and "Add Profile Entry" with appropriate German strings (e.g., "Assign Payout" → "Zahlung zuweisen", "Beneficiary Details" → "Begünstigteninformationen" or similar) ensuring wording matches existing German button/menu phrasing used elsewhere for consistency.src/assets/translations/de-DE.json-563-571 (1)
563-571:⚠️ Potential issue | 🟡 MinorTranslate new remittance button labels to German.
Several newly added button labels (e.g., “Assign Payout”, “Confirm Payment”, “New Remittance”, “Print Receipt”, “Validate Recipient”, “View Receipt”, “Add Entry”, “Retry”) are still English, which will surface mixed-language UI in de-DE. Please localize these or confirm the intended fallback behavior.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/de-DE.json` around lines 563 - 571, The de-DE translation file contains several untranslated keys ("Assign Payout", "Confirm Payment", "New Remittance", "Print Receipt", "Validate Recipient", "View Receipt", "Add Entry", "Retry") that must be localized; update the values for these JSON keys in src/assets/translations/de-DE.json to proper German strings (e.g., "Assign Payout" -> "Auszahlung zuweisen", "Confirm Payment" -> "Zahlung bestätigen", "New Remittance" -> "Neue Überweisung", "Print Receipt" -> "Quittung drucken", "Validate Recipient" -> "Empfänger validieren", "View Receipt" -> "Quittung anzeigen", "Add Entry" -> "Eintrag hinzufügen", "Retry" -> "Erneut versuchen") or change them to the intended fallback behavior if English should be preserved, ensuring the JSON keys remain unchanged (use the literal keys shown) and the values are valid German strings.src/assets/translations/de-DE.json-3926-3927 (1)
3926-3927:⚠️ Potential issue | 🟡 MinorEnsure “Process Remittance” is translated consistently.
“Process Remittance” appears here in English while other status keys are localized. Please translate it in de-DE and keep it consistent with the other sections where the same label appears.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/de-DE.json` around lines 3926 - 3927, The "Process Remittance" value is still in English; update the value in the de-DE JSON so it is translated and matches the same label used elsewhere in the codebase (replace the value for the key "Process Remittance" with the existing German translation used in other sections). If there is no existing translation to copy, set the value to "Zahlungsanweisung verarbeiten".src/assets/translations/de-DE.json-2872-2874 (1)
2872-2874:⚠️ Potential issue | 🟡 MinorLocalize remittance menu entries.
The new menu items “Remittances” and “Process Remittance” are still English. Please translate them for de-DE and align the phrasing with other occurrences of the same terms.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/de-DE.json` around lines 2872 - 2874, The keys "Remittances" and "Process Remittance" are still in English; replace their values in src/assets/translations/de-DE.json with the German translations used elsewhere in the repo (for example use "Remittances" -> "Überweisungen" and "Process Remittance" -> "Überweisung verarbeiten" or whatever exact phrasing the project uses) by searching existing occurrences and aligning wording/capitalization with other translations so the keys "Remittances" and "Process Remittance" match the project's established German terminology.src/assets/translations/de-DE.json-2880-2886 (1)
2880-2886:⚠️ Potential issue | 🟡 MinorTranslate new remittance placeholders.
Placeholders like “Enter document number”, “Enter first name (include middle name)”, “Enter remittance reference number”, and “Sender name” are still English. Please localize these for de-DE.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/de-DE.json` around lines 2880 - 2886, Replace the untranslated English values for the JSON keys by providing German text: update "Enter document number" -> "Geben Sie die Dokumentnummer ein", "Enter first name (include middle name)" -> "Geben Sie den Vornamen ein (einschließlich Zweitnamen)", "Enter last name" -> "Geben Sie den Nachnamen ein", "Enter remittance reference number" -> "Geben Sie die Überweisungsreferenznummer ein", and "Sender name" -> "Name des Absenders"; ensure you only change the values (right-hand side strings) for those keys in the translations JSON.src/assets/translations/de-DE.json-3610-3627 (1)
3610-3627:⚠️ Potential issue | 🟡 MinorLocalize remittance helper/error text.
The new helper and error messages are still English (e.g., “This remittance has already been paid successfully.”, “Failed to confirm payment…”, “Search and assign this beneficiary…”). These are high-visibility strings; please translate them to German or route through the localization pipeline.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/de-DE.json` around lines 3610 - 3627, Several remittance helper/error strings remain in English in the translations file; translate the listed keys into German or ensure they use the localization pipeline. Update the values for keys "This remittance has a terminal status and cannot be processed further.", "This remittance has already been paid successfully.", "Review the transaction and recipient details below, then assign the payout.", "Please review the details carefully before confirming the payment.", "Register the transactional profile for the beneficiary. Add entries for individuals or legal entities.", "No transactional profile entries yet. Add one below.", "Click to remove", "Recipient is not valid for this transaction. Please check the details.", "Recipient validation failed. Please check the document details and try again.", "Missing required information. Please try again.", "Failed to confirm payment. Please try again or contact support.", "Failed to assign payout. Please try again.", "Remittance not found. Please check the reference number and try again.", "Unable to load vendors. Please check your connection and try again.", "Search and assign this beneficiary to an existing Mifos client account", "Failed to search clients. Please try again.", and "Process Remittance" with proper German translations (or route their usages through the i18n/localization helper) so the de-DE.json contains German text for each key.src/assets/translations/de-DE.json-2717-2736 (1)
2717-2736:⚠️ Potential issue | 🟡 MinorTranslate new remittance input/validation terms.
Several new input/validation labels are still English (e.g., “Reference ID is required”, “Vendor”, “Voter ID”, “National Identity Card Number”, “Economic Activity”, “Avg Amount/Transaction”, “Sender Registry”, “External Reference ID”). These are user-facing and should be localized in de-DE.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/de-DE.json` around lines 2717 - 2736, Several user-facing validation/input labels in the de-DE JSON still contain English values; update the translation values for the keys "Reference ID is required", "Vendor", "Vendor is required", "Voter ID", "National Identity Card Number", "State", "Municipality", "Locality", "New Locality", "Occupation", "Economic Activity", "Entity Member", "# Remittance", "Avg Amount/Transaction", "# Senders", "Sender Registry", "Individual", "Legal Entity", "External Reference ID" to their German equivalents (e.g., "Reference ID is required" -> "Referenz-ID ist erforderlich", "Vendor" -> "Anbieter"/"Verkäufer" as appropriate, "Voter ID" -> "Wähler-ID", "National Identity Card Number" -> "Personalausweisnummer", "Economic Activity" -> "Wirtschaftliche Tätigkeit", "Avg Amount/Transaction" -> "Durchschn. Betrag/Transaktion", "Sender Registry" -> "Absenderregister", "External Reference ID" -> "Externe Referenz-ID", etc.); locate these keys in the de-DE translation object and replace the English strings with the correct German translations so the UI displays localized text.src/assets/translations/ne-NE.json-564-571 (1)
564-571:⚠️ Potential issue | 🟡 MinorAll new remittance keys carry English placeholder values — Nepali-speaking users will see untranslated UI text.
Every new key added across the
buttons,heading,inputs,menus,placeholders,text, andtooltipssections is set to its English source string (e.g."Assign Payout": "Assign Payout","Confirm Payment": "Confirm Payment", etc.). Only two of the ~70 added keys actually have Nepali translations:"Pending Tasks": "बाँकी कार्यहरू"(line 1306) and"INACTIVE": "निष्क्रिय"(line 3924). Every remittance-workflow surface — buttons, headings, inputs, menu items, placeholders, instructional text, and tooltips — will render raw English in the ne-NE locale until these are translated.If this is an intentional incremental approach (sync keys now, translate later), please track the outstanding translations in a follow-up issue so they are not forgotten.
Also applies to: 1307-1329, 2714-2732, 2868-2870, 2877-2882, 3611-3627, 3925-3925
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/ne-NE.json` around lines 564 - 571, The ne-NE JSON has many new keys still using English values (e.g. "Assign Payout", "Confirm Payment", "New Remittance", "Print Receipt", "Validate Recipient", "View Receipt", "Add Entry", "Retry") causing untranslated UI; update the values to their Nepali translations for all new keys across the buttons/headings/inputs/menus/placeholders/text/tooltips sections (use the existing translated keys "Pending Tasks" and "INACTIVE" as references) or, if intentional, create a tracked follow-up issue listing every untranslated key (include the exact key names like "Assign Payout", "Confirm Payment", etc.) so localization owners can complete translations later.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@src/assets/translations/cs-CS.json`:
- Around line 564-571: The cs-CS.json file contains remittance keys (e.g.,
"Assign Payout", "Confirm Payment", "New Remittance", "Print Receipt", "Validate
Recipient", "View Receipt", "Add Entry", "Retry" and any longer strings such as
"This remittance has a terminal status...") that are still English; update each
key's value to the correct Czech translation (or, if an approved translation is
not yet available, replace the English value with a clear placeholder like
"TODO_TRANSLATE_CZ: <English text>" so reviewers know it’s intentionally
untranslated), and apply the same approach consistently across the other
affected locale files (de-DE, fr-FR, it-IT, ko-KO, lt-LT, lv-LV, ne-NE, pt-PT,
sw-SW) ensuring every remittance-related key is either translated or marked with
the TODO_PREFIX so missing translations are explicit.
In `@src/assets/translations/ko-KO.json`:
- Around line 564-571: Several remittance-related translation values under
labels.buttons, labels.heading, labels.inputs, labels.menus,
labels.placeholders, labels.text and tooltips were left as English source
strings (e.g., "Assign Payout", "Confirm Payment", "New Remittance",
"Beneficiary Details", "Vendor", "Remittances", "Enter document number", etc.);
either replace each English value with the proper Korean translation for those
keys in src/assets/translations/ko-KO.json or, if translations are not yet
available, add a clear TODO comment in the PR and update the JSON values to an
explicit placeholder marker (e.g., "[ENGLISH - TRANSLATION PENDING]") for every
affected key and open a follow-up task/issue tracking the ~67 missing
translations so reviewers know these are intentional placeholders.
In `@src/assets/translations/lv-LV.json`:
- Around line 3926-3927: Update the Latvian translations in lv-LV.json: replace
the value for the key "INACTIVE" from "NEAKTIVS" to the correct Latvian spelling
"NEAKTĪVS" (note the ī), and translate the "Process Remittance" entry from
English to Latvian (e.g., "Process Remittance": "Apstrādāt pārvedumu" or another
approved Latvian phrasing) so both keys are fully localized.
- Around line 563-571: Replace the English values in lv-LV.json for the
remittance flow keys with Latvian translations: update "Assign Payout" →
"Piešķirt izmaksu", "Confirm Payment" → "Apstiprināt maksājumu", "New
Remittance" → "Jauns pārskaitījums", "Print Receipt" → "Drukāt kvīti", "Validate
Recipient" → "Pārbaudīt saņēmēju", "View Receipt" → "Skatīt kvīti", "Add Entry"
→ "Pievienot ierakstu", and "Retry" → "Mēģināt vēlreiz"; edit the string values
in the existing keys (same keys: "Assign Payout", "Confirm Payment", "New
Remittance", "Print Receipt", "Validate Recipient", "View Receipt", "Add Entry",
"Retry") in src/assets/translations/lv-LV.json and commit the updated JSON.
---
Duplicate comments:
In `@src/assets/translations/cs-CS.json`:
- Around line 2717-2735: The new entries under labels.inputs in
src/assets/translations/cs-CS.json currently have English-only values (e.g.,
"Vendor", "Municipality", "# Remittance"); update each value to the correct
Czech translation while keeping the JSON keys unchanged — for example replace
"Vendor": "Vendor" with "Vendor": "Prodejce", "Municipality": "Obec", "#
Remittance": "# Odeslané částky" (and similarly translate "Reference ID is
required", "Voter ID", "National Identity Card Number", "State", "Locality",
"New Locality", "Occupation", "Economic Activity", "Entity Member", "Avg
Amount/Transaction", "# Senders", "Sender Registry", "Individual", "Legal
Entity", "External Reference ID") ensuring punctuation and token formats remain
intact.
- Around line 3611-3627: The labels.text section contains 17 keys whose values
are still English (e.g., "Failed to confirm payment. Please try again or contact
support.", "Recipient validation failed. Please check the document details and
try again.", "Process Remittance"); replace each English value with the correct
Czech translation for the corresponding UI string so the cs-CS.json locale is
fully localized, preserving the exact JSON keys and punctuation, keeping string
length/format where placeholders are used, and validating the JSON/encoding
after changes.
- Around line 1308-1330: The labels.heading entries (e.g., "Assign Payout",
"Beneficiary Details", "Remittance Details", "Payment Receipt", "Transaction
Summary", "Validated Recipient Information", etc.) are left untranslated —
replace the English string values with their Czech translations for all 23 keys
in this block so the JSON provides Czech UI text; ensure you update the value
side only (keep the keys unchanged) and preserve JSON formatting and escaping.
In `@src/assets/translations/lv-LV.json`:
- Around line 2878-2884: Translate the English placeholder values in the lv-LV
JSON for the keys "Enter document number", "Enter first name (include middle
name)", "Enter last name", "Enter remittance reference number", and "Sender
name" into Latvian; update their values (currently English) to appropriate
Latvian strings while leaving keys unchanged and preserving JSON formatting and
surrounding entries like "Enter your password" and "# Remittance".
- Around line 2715-2734: The listed new translation keys (e.g., "Reference ID is
required", "Vendor", "Vendor is required", "Voter ID", "National Identity Card
Number", "State", "Municipality", "Locality", "New Locality", "Occupation",
"Economic Activity", "Entity Member", "# Remittance", "Avg Amount/Transaction",
"# Senders", "Sender Registry", "Individual", "Legal Entity", "External
Reference ID") are still in English; replace each English value with the correct
Latvian translation for the lv-LV resource (leave the keys unchanged) so the UI
displays Latvian text—for example provide Latvian equivalents for "#
Remittance", "Avg Amount/Transaction", "Reference ID is required", "Vendor is
required", "National Identity Card Number", etc., ensuring proper diacritics and
grammatical forms used elsewhere in the file.
- Around line 1308-1331: The JSON translation entries for remittance-related
keys ("Pending Tasks", "Assign Payout", "Assign to Mifos Client", "Beneficiary
Details", "Confirm Payment", "Confirm Payout", "Confirmation Details", "Payment
Receipt", "Payment Successful", "Process Remittance", "Recipient Details",
"Remittance Details", "Search Beneficiary", "Search Remittance", "Transaction",
"Transaction Status", "Transaction Summary", "Transactional Profile", "Validated
Recipient Information", "Recipient", "Payout Assignment", "Identification",
"Professional Information", "Add Profile Entry") are still in English; update
their values to the correct Latvian translations (replace the right-hand side
strings) so the UI is fully localized while keeping the keys unchanged.
- Around line 3612-3629: The listed remittance strings in
src/assets/translations/lv-LV.json are still English; update the JSON values for
the keys (e.g., "UploadDocumentHint", "This remittance has a terminal status and
cannot be processed further.", "This remittance has already been paid
successfully.", "Review the transaction and recipient details below, then assign
the payout.", "Please review the details carefully before confirming the
payment.", "Register the transactional profile for the beneficiary. Add entries
for individuals or legal entities.", "No transactional profile entries yet. Add
one below.", "Click to remove", "Recipient is not valid for this transaction.
Please check the details.", "Recipient validation failed. Please check the
document details and try again.", "Missing required information. Please try
again.", "Failed to confirm payment. Please try again or contact support.",
"Failed to assign payout. Please try again.", "Remittance not found. Please
check the reference number and try again.", "Unable to load vendors. Please
check your connection and try again.", "Search and assign this beneficiary to an
existing Mifos client account", "Failed to search clients. Please try again.",
"Process Remittance") with correct Latvian translations, ensuring punctuation
and capitalization match existing locale style; save the file as valid JSON and
run the localization/i18n checks or build to confirm no missing keys or syntax
errors.
shubhamkumar9199
force-pushed
the
feat/remittance-translations
branch
from
81bd215 to
af8ba27
Compare
There was a problem hiding this comment.
Actionable comments posted: 13
🧹 Nitpick comments (1)
src/assets/translations/ne-NE.json (1)
2452-2452: Near-duplicate case-split keys"Select Entity"/"Select entity"with different Nepali wordsThe pre-existing key
"Select Entity"(line 2452) uses"निकाय चयन गर्नुहोस्", while the new key"Select entity"(line 2713) uses"इकाई चयन गर्नुहोस्". Both "निकाय" and "इकाई" mean "entity" in Nepali. Because these keys differ only in capitalisation, components that reference them may do so inconsistently, and translators working on the file later may not notice the second entry. Confirm whether both keys are truly needed in the application; if so, ensure their Nepali translations are intentionally different.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/ne-NE.json` at line 2452, The JSON contains near-duplicate keys "Select Entity" and "Select entity" with inconsistent Nepali translations ("निकाय चयन गर्नुहोस्" vs "इकाई चयन गर्नुहोस्"); locate both keys ("Select Entity" and "Select entity") and either consolidate them to a single canonical key or explicitly document why both variants are required, then make their Nepali translations consistent and intentional (if one key is canonical, remove or alias the other; if both are needed, update the translations so they reflect distinct meanings and add a short comment/note to clarify usage).
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@src/assets/translations/de-DE.json`:
- Around line 2886-2893: Replace the untranslated value "# Remittance" with its
German equivalent to match the rest of the inputs; locate the JSON key whose
value is "# Remittance" (near "Enter remittance reference number" and "Enter
document number") and change the value to the German placeholder "# Überweisung"
so the UI shows a consistent German label.
In `@src/assets/translations/es-CL.json`:
- Around line 2877-2879: The "Tasks" translation value is left in English;
update the JSON entry for the key "Tasks" so the value is translated to Spanish
(e.g., change the value to "Tareas") to keep locale consistency—edit the object
entry with key "Tasks" near the other keys ("Remittances", "Process Remittance")
to replace "Tasks" with the Spanish translation.
- Around line 2885-2892: Replace the English value for the translation key "#
Remittance" with the Spanish localized string to match the other remittance
entries (e.g., change the value from "# Remittance" to "# Remesa"); update the
JSON entry for the key "# Remittance" so the value aligns with existing
remittance translations like "Ingrese número de referencia de remesa" and ensure
the JSON syntax/quoting remains valid around the "Enter your password", "Enter
document number", and adjacent entries.
In `@src/assets/translations/it-IT.json`:
- Around line 2875-2877: The "Tasks" translation key currently has an English
value ("Tasks"); update the value for the "Tasks" key to the proper Italian
translation (e.g., "Attività") so the menu reads consistently with the
surrounding keys like "Remittances" and "Process Remittance"; locate the "Tasks"
key in the JSON (near "Remittances" and "Process Remittance") and replace its
value with "Attività", ensuring the JSON string quoting and encoding remain
valid.
- Around line 2884-2889: The JSON localization contains the English placeholder
key "# Remittance" which should be translated to Italian to match the existing
label (“# Rimessa”); update the translation entry for the key "# Remittance"
(and any duplicate keys) in the it-IT translations (currently shown as "#
Remittance": "# Remittance") to use the Italian string "# Rimessa" so it aligns
with the label used elsewhere.
In `@src/assets/translations/ko-KO.json`:
- Line 2885: Placeholder value for the key "# Remittance" under
labels.placeholders is still in English; update its value to the Korean
translation "# 송금" to match the semantically identical entry in labels.inputs
and ensure consistency for Korean locale by replacing the value for the "#
Remittance" key in the JSON.
In `@src/assets/translations/lv-LV.json`:
- Around line 2876-2878: The "Tasks" translation key in
src/assets/translations/lv-LV.json is still English; replace the value for the
"Tasks" key with the correct Latvian translation (e.g., "Uzdevumi") so the menu
label is localized; ensure the JSON entry remains syntactically valid and
matches the existing key "Tasks".
- Around line 2884-2891: Replace the English placeholder value for the
translation key "# Remittance" with the Latvian version used elsewhere ("#
Pārvedums"); update the entry for the key "# Remittance" in the translations
object so its value is "# Pārvedums" to maintain consistent localization.
In `@src/assets/translations/ne-NE.json`:
- Around line 1310-1311: The two translation keys "Confirm Payment" and "Confirm
Payout" currently map to the identical Nepali string; update the "Confirm
Payout" entry in ne-NE.json so it uses a distinct Nepali phrase (e.g., change
the value for "Confirm Payout" from "भुक्तानी पुष्टि गर्नुहोस्" to "भुक्तानी
वितरण पुष्टि गर्नुहोस्" or another appropriate distinct phrasing) to preserve
the semantic difference between Payment and Payout in the remittance workflow.
- Line 571: The "Retry" translation is inconsistent: in labels.buttons the key
"Retry" uses the imperative "पुनः प्रयास गर्नुहोस्" while in labels.inputs it
uses the shorter "पुनः प्रयास"; update the labels.inputs "Retry" entry to the
imperative form "पुनः प्रयास गर्नुहोस्" so both keys (labels.buttons."Retry" and
labels.inputs."Retry") are consistent when the inputs entry is also
action-oriented; locate the "Retry" keys in the JSON (symbols: labels.buttons,
labels.inputs, "Retry") and replace the inputs value to match the buttons value.
- Line 2883: The key "# Remittance" in labels.placeholders is left untranslated
— replace the English placeholder string "# Remittance" with the Nepali
transliteration "# रेमिट्यान्स" (the same value already present at line ~2726)
in this file's labels.placeholders entry; then mirror this fix across the other
affected locale files (sw-SW, pt-PT, lv-LV, ko-KO, lt-LT, it-IT, fr-FR, es-CL,
de-DE, cs-CS) by substituting their English "# Remittance" placeholder with the
appropriate translated/transliterated value for each locale to ensure consistent
UI text.
In `@src/assets/translations/sw-SW.json`:
- Around line 2882-2886: The translation key "# Remittance" is left in English
and should be translated to Swahili to avoid mixed-language UI; update the JSON
entry for the key "# Remittance" to its Swahili equivalent (for example "#
Uhawilishaji") so it matches the surrounding entries like "Enter remittance
reference number" and other Swahili labels.
- Around line 3928-3932: Remove the duplicate "Process Remittance" entry in the
JSON "text" block by deleting the redundant key/value pair ("Process
Remittance": "Chakata uhawilishaji") so only the original "Process Remittance"
entry remains; ensure the JSON stays valid (no trailing commas) after removal
and that the remaining translation at the original "Process Remittance" key is
correct.
---
Duplicate comments:
In `@src/assets/translations/lv-LV.json`:
- Around line 3933-3934: The translation value for the "INACTIVE" key is missing
the Latvian long vowel; update the value for the "INACTIVE" JSON key from
"NEAKTIVS" to the correct spelling "NEAKTĪVS" (preserve surrounding JSON
formatting and commas, e.g., alongside the "Process Remittance" entry).
---
Nitpick comments:
In `@src/assets/translations/ne-NE.json`:
- Line 2452: The JSON contains near-duplicate keys "Select Entity" and "Select
entity" with inconsistent Nepali translations ("निकाय चयन गर्नुहोस्" vs "इकाई
चयन गर्नुहोस्"); locate both keys ("Select Entity" and "Select entity") and
either consolidate them to a single canonical key or explicitly document why
both variants are required, then make their Nepali translations consistent and
intentional (if one key is canonical, remove or alias the other; if both are
needed, update the translations so they reflect distinct meanings and add a
short comment/note to clarify usage).
Comment on lines
3928
to
3932
| "ACTIVE": "INAYOENDELEA", | ||
| "PENDING": "INAKARIBISHWA", | ||
| "INACTIVE": "HAITUMIKI" | ||
| "INACTIVE": "HAITUMIKI", | ||
| "Process Remittance": "Chakata uhawilishaji" | ||
| }, |
There was a problem hiding this comment.
Remove the duplicate Process Remittance key in the text block.
Process Remittance already exists at Line 3633; the duplicate at Line 3931 creates conflicting keys in the same JSON object (undefined behavior and potential lint failures).
✅ Suggested fix
- "INACTIVE": "HAITUMIKI",
- "Process Remittance": "Chakata uhawilishaji"
+ "INACTIVE": "HAITUMIKI"📝 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
| "ACTIVE": "INAYOENDELEA", | |
| "PENDING": "INAKARIBISHWA", | |
| "INACTIVE": "HAITUMIKI" | |
| "INACTIVE": "HAITUMIKI", | |
| "Process Remittance": "Chakata uhawilishaji" | |
| }, | |
| "ACTIVE": "INAYOENDELEA", | |
| "PENDING": "INAKARIBISHWA", | |
| "INACTIVE": "HAITUMIKI" | |
| }, |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@src/assets/translations/sw-SW.json` around lines 3928 - 3932, Remove the
duplicate "Process Remittance" entry in the JSON "text" block by deleting the
redundant key/value pair ("Process Remittance": "Chakata uhawilishaji") so only
the original "Process Remittance" entry remains; ensure the JSON stays valid (no
trailing commas) after removal and that the remaining translation at the
original "Process Remittance" key is correct.
af8ba27 to
b1330bb
Compare
There was a problem hiding this comment.
Actionable comments posted: 8
🧹 Nitpick comments (1)
src/assets/translations/ko-KO.json (1)
2716-2716: Inconsistent romanization of "entity" between new and existing keys.Line 2716 (new):
"Select entity": "엔티티 선택"uses엔티티, while the existing line 2455"Select Entity": "엔터티 선택"uses엔터티. Both are romanizations of "entity", but mixing them within the same file is inconsistent.엔터티is the more widely used Korean transliteration.🔧 Suggested fix
- "Select entity": "엔티티 선택", + "Select entity": "엔터티 선택",🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/ko-KO.json` at line 2716, The translation for the key "Select entity" uses the inconsistent romanization "엔티티 선택"; update its value to use the same romanization as the existing key "Select Entity" (i.e., change "엔티티 선택" to "엔터티 선택") so both keys use "엔터티" consistently across the file.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@src/assets/translations/es-MX.json`:
- Around line 3634-3635: Update the value for the "UploadDocumentHint"
translation to use the formal imperative for consistency with other strings;
replace "Sube un PDF o imagen para generar una vista previa." with "Suba un PDF
o imagen para generar una vista previa." so the "UploadDocumentHint" key matches
the formal tone used elsewhere.
In `@src/assets/translations/fr-FR.json`:
- Around line 563-571: The translation for the "Assign Payout" key uses
"Attribuer le paiement" but other remittance-related keys (e.g., "New
Remittance", "Confirm Payment", "Validate Recipient", "View Receipt") use
"versement" terminology; update the value for the "Assign Payout" JSON key to
use "versement" (for example "Attribuer le versement") so it matches the rest of
the remittance copy and keeps terminology consistent across the UI.
- Around line 1314-1334: The French translations currently map both
"Beneficiary" and "Recipient" to "Bénéficiaire"; update the "Recipient" entries
to use "Destinataire" to preserve the distinct meaning—specifically change the
value for the "Recipient" key to "Destinataire" and adjust related keys that
mention recipient (e.g., "Recipient Details" and "Validated Recipient
Information") to use "Détails du destinataire" and "Informations du destinataire
validées" (or equivalent consistent phrasing) while leaving "Beneficiary" and
its related keys as "Bénéficiaire"/"Détails du bénéficiaire".
In `@src/assets/translations/it-IT.json`:
- Around line 560-570: The "Advanced Search" translation value is still English;
update the JSON entry for the key "Advanced Search" to the Italian translation
(e.g., "Ricerca avanzata") so it matches the adjacent localized strings ("Show
advanced search", "Hide advanced search"); ensure you only change the value for
the "Advanced Search" key and preserve JSON formatting and quotes.
In `@src/assets/translations/ko-KO.json`:
- Around line 1309-1332: Two distinct UI keys have identical Korean translations
which can confuse users: "Beneficiary Details" and "Recipient Details" both map
to "수취인 상세정보", and "Assign Payout" and "Payout Assignment" both map to "지급 배정".
Update the translations so each key is semantically distinct—e.g., change the
"Recipient Details" translation for the "Recipient Details" key to "수신자 상세정보"
(or another appropriate differentiator) and change the "Payout Assignment"
translation for the "Payout Assignment" key to "지급 배정 정보" (keeping "Assign
Payout" as "지급 배정" if that remains the action label); modify the values for the
keys "Beneficiary Details", "Recipient Details", "Assign Payout", and "Payout
Assignment" accordingly in the JSON.
In `@src/assets/translations/ne-NE.json`:
- Around line 1320-1322: Replace the inconsistent Nepali term "कारोबार" with the
preferred "लेनदेन" for the translation keys "Transaction", "Transaction Status",
and "Transaction Summary" (and the other affected entries around the same block
noted in the comment) so they match existing strings like "View Transactions"
and "Transaction Details"; update the values for the keys "Transaction",
"Transaction Status", and "Transaction Summary" to use "लेनदेन" wording
consistently across the file.
In `@src/assets/translations/pt-PT.json`:
- Around line 2883-2890: Update the Portuguese (pt-PT) translation for the key
"Enter your password" to use PT‑PT wording: replace the current value "Digite
sua senha" with "Introduza a sua palavra‑passe" so the mapping "Enter your
password": "Introduza a sua palavra‑passe" appears in
src/assets/translations/pt-PT.json.
- Around line 1307-1330: The Portuguese translation for the key "Assign to Mifos
Client" is awkward; update its value from "Atribuir a cliente Mifos" to the
natural PT‑PT phrasing "Atribuir ao cliente Mifos" by editing the value for the
"Assign to Mifos Client" entry in src/assets/translations/pt-PT.json.
---
Duplicate comments:
In `@src/assets/translations/lv-LV.json`:
- Around line 3933-3934: The translation key "INACTIVE" in
src/assets/translations/lv-LV.json currently uses "NEAKTIVS" without the proper
Latvian long vowel; update the value for the "INACTIVE" key to use the correct
diacritic form "NĪAKTIVS" (or the correct Latvian word "NEAKTĪVS" if that was
intended) so the string contains the proper Ī character; locate the "INACTIVE"
entry and replace its value accordingly, ensuring the JSON remains valid and
encoded in UTF-8.
In `@src/assets/translations/sw-SW.json`:
- Around line 3928-3931: There is a duplicate translation key "Process
Remittance" in the translations JSON (the second occurrence near the shown diff
will overwrite the earlier one); remove the duplicate entry in the shown block
so only the original "Process Remittance" key/value remains in the text object,
ensuring you edit the block that contains "ACTIVE"/"PENDING"/"INACTIVE" and
delete the "Process Remittance" line (leave the first occurrence around the
earlier "text" section intact).
---
Nitpick comments:
In `@src/assets/translations/ko-KO.json`:
- Line 2716: The translation for the key "Select entity" uses the inconsistent
romanization "엔티티 선택"; update its value to use the same romanization as the
existing key "Select Entity" (i.e., change "엔티티 선택" to "엔터티 선택") so both keys
use "엔터티" consistently across the file.
improve improve improve
shubhamkumar9199
force-pushed
the
feat/remittance-translations
branch
from
b1330bb to
f1eacdb
Compare
There was a problem hiding this comment.
Actionable comments posted: 4
🧹 Nitpick comments (1)
src/assets/translations/ko-KO.json (1)
2716-2741:"Occupation"and"Profession"share the same Korean translation"직업".The newly added
"Occupation": "직업"(line 2726) duplicates the pre-existing"Profession": "직업"(line 2316). In Korean직업is the natural translation for both, so this is linguistically expected. However, if both labels ever render on the same form (e.g., a combined client profile), end users will see two identical Korean strings for conceptually different fields. Consider distinguishing them only if the workflow surfaces both simultaneously — e.g.,"직종"(type of work/occupation category) for"Occupation"and keeping"직업"for"Profession".🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/assets/translations/ko-KO.json` around lines 2716 - 2741, The keys "Occupation" and "Profession" currently share the same Korean translation "직업", which can be confusing if both labels appear together; update the translation for one key to a distinct, context-appropriate term (for example change the "Occupation" value to "직종" while keeping "Profession" as "직업" or choose the opposite depending on the UI context), and ensure the change is applied to the "Occupation" (and/or "Profession") entry so forms that render both labels display distinct Korean strings; if unsure, consult the product designer to confirm which key should use "직종" vs "직업".
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@src/assets/translations/ko-KO.json`:
- Around line 1309-1332: The translations for "Recipient" and "Recipient
Details" are inconsistent ("수취인" vs "수신자"); update the "Recipient" key
translation to "수신자" to match "Recipient Details" (keep "Beneficiary Details" as
"수취인 상세정보" so beneficiary vs recipient remain distinct) so labels use the same
Korean root when they refer to the same actor.
In `@src/assets/translations/lt-LT.json`:
- Around line 2715-2740: The translation for the key "Select entity" uses
"objektą" which is inconsistent with other keys like "Entity Member" ("Subjekto
narys") and any other "Entity" usages; pick a single Lithuanian term (e.g.,
"subjektas" or "objektas") and update the value for "Select entity" and all
other keys that reference "Entity" or "entity" in this JSON (notably "Select
entity" and "Entity Member") so they use the same chosen term and grammatical
form throughout the file to ensure consistent UX terminology.
In `@src/assets/translations/ne-NE.json`:
- Around line 1320-1324: Replace the inconsistent translation for the key whose
value is "Transactional Profile" so it uses the same "लेनदेन" terminology as
other remittance entries; locate the JSON entry with the value "Transactional
Profile" and change its Nepali string to use "लेनदेन" (e.g., "लेनदेन प्रोफाइल"
or another equivalent using लेनदेन) so the remittance block uses consistent
terminology across "Transaction", "Transaction Status", and related keys.
- Around line 2726-2728: Replace the translation string for the "Avg
Amount/Transaction" key so it uses the same term "लेनदेन" used elsewhere for
remittance transactions; locate the "Avg Amount/Transaction" entry in the
ne-NE.json snippet and change its value from "औसत रकम/कारोबार" to something like
"औसत रकम/लेनदेन" to maintain consistent terminology with the remittance strings
(keep the surrounding keys "# Remittance" and "# Senders" unchanged).
---
Duplicate comments:
In `@src/assets/translations/fr-FR.json`:
- Around line 563-569: The French translation uses “bénéficiaire” for Recipient
in the remittance strings but the Pending Tasks block standardizes on
“destinataire”; update the translations so keys like "Validate Recipient" (and
any remittance-related guidance keys that currently translate Recipient as
"bénéficiaire" in the New Remittance block) use "destinataire" instead, ensuring
all occurrences in src/assets/translations/fr-FR.json are changed to match the
standardized term.
In `@src/assets/translations/lv-LV.json`:
- Around line 3933-3934: Replace the Latvian translation value for the
"INACTIVE" key from "NEAKTIVS" to the correct diacritic form "NEAKTĪVS" in the
translations JSON; ensure the file is saved with UTF-8 encoding so the "Ī"
character is preserved.
In `@src/assets/translations/sw-SW.json`:
- Around line 3928-3931: The file contains a duplicate "Process Remittance" key
in the translations JSON; remove the second occurrence shown in the diff (the
"Process Remittance": "Chakata uhawilishaji" entry) so only the original
definition (the one at the earlier "Process Remittance" key) remains in the
translations object; locate the duplicate by searching for the "Process
Remittance" key in the translations object and delete the duplicate entry to
avoid last-write-wins behavior.
---
Nitpick comments:
In `@src/assets/translations/ko-KO.json`:
- Around line 2716-2741: The keys "Occupation" and "Profession" currently share
the same Korean translation "직업", which can be confusing if both labels appear
together; update the translation for one key to a distinct, context-appropriate
term (for example change the "Occupation" value to "직종" while keeping
"Profession" as "직업" or choose the opposite depending on the UI context), and
ensure the change is applied to the "Occupation" (and/or "Profession") entry so
forms that render both labels display distinct Korean strings; if unsure,
consult the product designer to confirm which key should use "직종" vs "직업".
Comment on lines
+1309
to
+1332
| "Pending Tasks": "보류 중인 작업", | ||
| "Assign Payout": "지급 배정", | ||
| "Assign to Mifos Client": "Mifos 고객에게 배정", | ||
| "Beneficiary Details": "수취인 상세정보", | ||
| "Confirm Payment": "결제 확인", | ||
| "Confirm Payout": "지급 확인", | ||
| "Confirmation Details": "확인 상세정보", | ||
| "Payment Receipt": "결제 영수증", | ||
| "Payment Successful": "결제 완료", | ||
| "Process Remittance": "송금 처리", | ||
| "Recipient Details": "수신자 상세정보", | ||
| "Remittance Details": "송금 상세정보", | ||
| "Search Beneficiary": "수취인 검색", | ||
| "Search Remittance": "송금 검색", | ||
| "Transaction": "거래", | ||
| "Transaction Status": "거래 상태", | ||
| "Transaction Summary": "거래 요약", | ||
| "Transactional Profile": "거래 프로필", | ||
| "Validated Recipient Information": "확인된 수취인 정보", | ||
| "Recipient": "수취인", | ||
| "Payout Assignment": "지급 배정 정보", | ||
| "Identification": "신원 확인", | ||
| "Professional Information": "직업 정보", | ||
| "Add Profile Entry": "프로필 항목 추가" |
There was a problem hiding this comment.
Past heading-duplication concern is now resolved; one new minor inconsistency introduced.
The previously unresolved review comment (identical translations for "Beneficiary Details" / "Recipient Details" and "Assign Payout" / "Payout Assignment") is addressed in the current code — all four keys now have semantically distinct Korean values.
However, a smaller inconsistency was introduced as a side-effect of the fix: the standalone "Recipient" key (line 1328) is translated as "수취인", while "Recipient Details" (line 1319) uses "수신자 상세정보" — a different Korean root word for "recipient". In Korean financial UI, 수취인 (payee/beneficiary) and 수신자 (receiver) carry slightly different connotations. If both labels appear on the same screen, Korean users may read them as referring to different people.
Suggested alignment (choose one root consistently):
🔧 Option A — Align "Recipient Details" to match "Recipient" (수취인)
- "Recipient Details": "수신자 상세정보",
+ "Recipient Details": "수취인 상세정보",(Note: this would re-introduce the original duplication with "Beneficiary Details". Only viable if Recipient ≡ Beneficiary in this workflow.)
🔧 Option B — Align standalone "Recipient" to match "Recipient Details" (수신자)
- "Recipient": "수취인",
+ "Recipient": "수신자",(Preferred if "Recipient" and "Beneficiary" are distinct actors in this workflow.)
📝 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
| "Pending Tasks": "보류 중인 작업", | |
| "Assign Payout": "지급 배정", | |
| "Assign to Mifos Client": "Mifos 고객에게 배정", | |
| "Beneficiary Details": "수취인 상세정보", | |
| "Confirm Payment": "결제 확인", | |
| "Confirm Payout": "지급 확인", | |
| "Confirmation Details": "확인 상세정보", | |
| "Payment Receipt": "결제 영수증", | |
| "Payment Successful": "결제 완료", | |
| "Process Remittance": "송금 처리", | |
| "Recipient Details": "수신자 상세정보", | |
| "Remittance Details": "송금 상세정보", | |
| "Search Beneficiary": "수취인 검색", | |
| "Search Remittance": "송금 검색", | |
| "Transaction": "거래", | |
| "Transaction Status": "거래 상태", | |
| "Transaction Summary": "거래 요약", | |
| "Transactional Profile": "거래 프로필", | |
| "Validated Recipient Information": "확인된 수취인 정보", | |
| "Recipient": "수취인", | |
| "Payout Assignment": "지급 배정 정보", | |
| "Identification": "신원 확인", | |
| "Professional Information": "직업 정보", | |
| "Add Profile Entry": "프로필 항목 추가" | |
| "Pending Tasks": "보류 중인 작업", | |
| "Assign Payout": "지급 배정", | |
| "Assign to Mifos Client": "Mifos 고객에게 배정", | |
| "Beneficiary Details": "수취인 상세정보", | |
| "Confirm Payment": "결제 확인", | |
| "Confirm Payout": "지급 확인", | |
| "Confirmation Details": "확인 상세정보", | |
| "Payment Receipt": "결제 영수증", | |
| "Payment Successful": "결제 완료", | |
| "Process Remittance": "송금 처리", | |
| "Recipient Details": "수신자 상세정보", | |
| "Remittance Details": "송금 상세정보", | |
| "Search Beneficiary": "수취인 검색", | |
| "Search Remittance": "송금 검색", | |
| "Transaction": "거래", | |
| "Transaction Status": "거래 상태", | |
| "Transaction Summary": "거래 요약", | |
| "Transactional Profile": "거래 프로필", | |
| "Validated Recipient Information": "확인된 수취인 정보", | |
| "Recipient": "수신자", | |
| "Payout Assignment": "지급 배정 정보", | |
| "Identification": "신원 확인", | |
| "Professional Information": "직업 정보", | |
| "Add Profile Entry": "프로필 항목 추가" |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@src/assets/translations/ko-KO.json` around lines 1309 - 1332, The
translations for "Recipient" and "Recipient Details" are inconsistent ("수취인" vs
"수신자"); update the "Recipient" key translation to "수신자" to match "Recipient
Details" (keep "Beneficiary Details" as "수취인 상세정보" so beneficiary vs recipient
remain distinct) so labels use the same Korean root when they refer to the same
actor.
Comment on lines
+2715
to
+2740
| "Select entity": "Pasirinkite objektą", | ||
| "Reference ID is required": "Nuorodos ID yra privalomas", | ||
| "Vendor": "Tiekėjas", | ||
| "Vendor is required": "Tiekėjas yra privalomas", | ||
| "Voter ID": "Rinkėjo ID", | ||
| "National Identity Card Number": "Asmens tapatybės kortelės numeris", | ||
| "State": "Valstija", | ||
| "Municipality": "Savivaldybė", | ||
| "Locality": "Vietovė", | ||
| "New Locality": "Nauja vietovė", | ||
| "Occupation": "Profesija", | ||
| "Economic Activity": "Ekonominė veikla", | ||
| "Entity Member": "Subjekto narys", | ||
| "# Remittance": "# Pervedimas", | ||
| "Avg Amount/Transaction": "Vid. suma/Sandoris", | ||
| "# Senders": "# Siuntėjai", | ||
| "Sender Registry": "Siuntėjų registras", | ||
| "Individual": "Fizinis asmuo", | ||
| "Legal Entity": "Juridinis asmuo", | ||
| "External Reference ID": "Išorinis nuorodos ID", | ||
| "Enter remittance reference number": "Įveskite pervedimo nuorodos numerį", | ||
| "Enter document number": "Įveskite dokumento numerį", | ||
| "Enter first name (include middle name)": "Įveskite vardą (įskaitant antrą vardą)", | ||
| "Enter last name": "Įveskite pavardę", | ||
| "Sender name": "Siuntėjo vardas", | ||
| "Retry": "Bandyti dar kartą" |
There was a problem hiding this comment.
Check terminology consistency for “entity”.
“Select entity” uses “objektą”; elsewhere in this locale, “Entity” appears with different terms. Please align to a single Lithuanian term to avoid mixed UX language.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@src/assets/translations/lt-LT.json` around lines 2715 - 2740, The translation
for the key "Select entity" uses "objektą" which is inconsistent with other keys
like "Entity Member" ("Subjekto narys") and any other "Entity" usages; pick a
single Lithuanian term (e.g., "subjektas" or "objektas") and update the value
for "Select entity" and all other keys that reference "Entity" or "entity" in
this JSON (notably "Select entity" and "Entity Member") so they use the same
chosen term and grammatical form throughout the file to ensure consistent UX
terminology.
Comment on lines
+1320
to
+1324
| "Transaction": "लेनदेन", | ||
| "Transaction Status": "लेनदेन स्थिति", | ||
| "Transaction Summary": "लेनदेन सारांश", | ||
| "Transactional Profile": "कारोबार प्रोफाइल", | ||
| "Validated Recipient Information": "प्रमाणित प्राप्तकर्ता जानकारी", |
There was a problem hiding this comment.
Align “Transactional Profile” with the “लेनदेन” terminology used elsewhere in this remittance block.
“Transaction”, “Transaction Status”, and the remittance text entries use “लेनदेन”, so keeping “Transactional Profile” aligned avoids mixed terminology in the same workflow.
🔧 Suggested tweak
- "Transactional Profile": "कारोबार प्रोफाइल",
+ "Transactional Profile": "लेनदेन प्रोफाइल",📝 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
| "Transaction": "लेनदेन", | |
| "Transaction Status": "लेनदेन स्थिति", | |
| "Transaction Summary": "लेनदेन सारांश", | |
| "Transactional Profile": "कारोबार प्रोफाइल", | |
| "Validated Recipient Information": "प्रमाणित प्राप्तकर्ता जानकारी", | |
| "Transaction": "लेनदेन", | |
| "Transaction Status": "लेनदेन स्थिति", | |
| "Transaction Summary": "लेनदेन सारांश", | |
| "Transactional Profile": "लेनदेन प्रोफाइल", | |
| "Validated Recipient Information": "प्रमाणित प्राप्तकर्ता जानकारी", |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@src/assets/translations/ne-NE.json` around lines 1320 - 1324, Replace the
inconsistent translation for the key whose value is "Transactional Profile" so
it uses the same "लेनदेन" terminology as other remittance entries; locate the
JSON entry with the value "Transactional Profile" and change its Nepali string
to use "लेनदेन" (e.g., "लेनदेन प्रोफाइल" or another equivalent using लेनदेन) so
the remittance block uses consistent terminology across "Transaction",
"Transaction Status", and related keys.
Comment on lines
+2726
to
+2728
| "# Remittance": "# रेमिट्यान्स", | ||
| "Avg Amount/Transaction": "औसत रकम/कारोबार", | ||
| "# Senders": "# पठाउनेहरू", |
There was a problem hiding this comment.
Keep “Avg Amount/Transaction” aligned with “लेनदेन”.
This block already uses “लेनदेन” for remittance transactions, so using the same term here improves consistency.
🔧 Suggested tweak
- "Avg Amount/Transaction": "औसत रकम/कारोबार",
+ "Avg Amount/Transaction": "औसत रकम/लेनदेन",📝 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
| "# Remittance": "# रेमिट्यान्स", | |
| "Avg Amount/Transaction": "औसत रकम/कारोबार", | |
| "# Senders": "# पठाउनेहरू", | |
| "# Remittance": "# रेमिट्यान्स", | |
| "Avg Amount/Transaction": "औसत रकम/लेनदेन", | |
| "# Senders": "# पठाउनेहरू", |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@src/assets/translations/ne-NE.json` around lines 2726 - 2728, Replace the
translation string for the "Avg Amount/Transaction" key so it uses the same term
"लेनदेन" used elsewhere for remittance transactions; locate the "Avg
Amount/Transaction" entry in the ne-NE.json snippet and change its value from
"औसत रकम/कारोबार" to something like "औसत रकम/लेनदेन" to maintain consistent
terminology with the remittance strings (keep the surrounding keys "#
Remittance" and "# Senders" unchanged).
IOhacker
approved these changes
Feb 22, 2026
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.
Add remittance-related translation keys to all non-English language files (cs-CS, de-DE, es-CL, es-MX, fr-FR, it-IT, ko-KO, lt-LT, lv-LV, ne-NE, pt-PT, sw-SW).
These keys were present in en-US.json but missing from all other language files, causing untranslated or missing text in the remittance workflow UI.
WEB-771
Checklist
Please make sure these boxes are checked before submitting your pull request - thanks!
If you have multiple commits please combine them into one commit by squashing them.
Read and understood the contribution guidelines at
web-app/.github/CONTRIBUTING.md.Summary by CodeRabbit