Context
During QA of a Togo deployment in fr_FR, several strings in spp_programs/i18n/fr.po render as machine-mangled half-French — the verb or noun was translated but the rest of the phrase was left in English, producing strings no native speaker would write. Affects every fr_FR deployment, not just ours.
Examples (currently in upstream 19.0)
Every line below is verified against spp_programs/i18n/fr.po@00f1e5a:
| msgid |
Current msgstr (wrong) |
Line |
Proposed |
In-Kind |
In-Type |
L5790-5791 |
Dons en nature |
Initial Amount |
Initial Montant |
L5972-5973 |
Montant initial |
Not Paid |
Not Payé |
L7104-7105 |
Non payé |
To Approve |
To Approuver |
L10100-10101 |
À approuver |
Verify Eligibility |
Verify Éligibilité |
L10530-10531 |
Vérifier l'éligibilité |
Prepare Entitlements |
Préparer Droits (in an embedded help string at L4738) |
— |
Préparer les droits |
The In-Kind issue cascades into ~9 related entries (In-Kind Entitlement, In-Kind Entitlement Approval, …, all currently In-Type Droit ...) — all at L5790–5832.
Where it hurts
All visible on the FSB program form and cycle form: state pipeline badges (To Approve, Distributed), action buttons (Verify Eligibility, Prepare Entitlements), financial summary fields (Initial Amount), and the In-Kind menu/program — i.e. the most heavily-used operator screens.
Workaround (downstream)
We've shipped a cross-module override in our downstream BOMS module's fr.po plus a force-reload migration with overwrite=True to correct these on our QA + UAT instances. This is fragile and per-deployment — fixing at source removes the need for downstream overrides.
Offer
We can supply reviewed Togo-French .po entries as a PR (already deployed and used in production-style QA). Maintainer call on whether to land as one batch or split per concern.
Related
Severity
MEDIUM — visibly unprofessional in any fr_FR deployment, not a functional blocker.
Context
During QA of a Togo deployment in
fr_FR, several strings inspp_programs/i18n/fr.porender as machine-mangled half-French — the verb or noun was translated but the rest of the phrase was left in English, producing strings no native speaker would write. Affects everyfr_FRdeployment, not just ours.Examples (currently in upstream
19.0)Every line below is verified against
spp_programs/i18n/fr.po@00f1e5a:msgstr(wrong)In-KindIn-TypeDons en natureInitial AmountInitial MontantMontant initialNot PaidNot PayéNon payéTo ApproveTo ApprouverÀ approuverVerify EligibilityVerify ÉligibilitéVérifier l'éligibilitéPrepare EntitlementsPréparer Droits(in an embedded help string at L4738)Préparer les droitsThe
In-Kindissue cascades into ~9 related entries (In-Kind Entitlement,In-Kind Entitlement Approval, …, all currentlyIn-Type Droit ...) — all at L5790–5832.Where it hurts
All visible on the FSB program form and cycle form: state pipeline badges (
To Approve,Distributed), action buttons (Verify Eligibility,Prepare Entitlements), financial summary fields (Initial Amount), and the In-Kind menu/program — i.e. the most heavily-used operator screens.Workaround (downstream)
We've shipped a cross-module override in our downstream BOMS module's
fr.poplus a force-reload migration withoverwrite=Trueto correct these on our QA + UAT instances. This is fragile and per-deployment — fixing at source removes the need for downstream overrides.Offer
We can supply reviewed Togo-French
.poentries as a PR (already deployed and used in production-style QA). Maintainer call on whether to land as one batch or split per concern.Related
total_amount_in_wordsignores user language.spp_programs,spp_registry,spp_change_request_v2,theme_openspp_muk, base.Severity
MEDIUM — visibly unprofessional in any
fr_FRdeployment, not a functional blocker.