You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue #350 found that the bulk translation fill in #340 introduced formal-register strings into the Hungarian catalogue, which had been consistently informal since well before #340. Twenty-eight msgstrs had to be rewritten in 4c14615 to put it back.
The same fill produced the other eighteen catalogues, and several of those languages draw the same T–V distinction: German (Sie/du), French (vous/tu), Spanish (usted/tú), Italian, Portuguese, Dutch, Polish, Czech, Russian among them. There is no reason to think Hungarian was uniquely affected, and we only caught it because a native speaker raised it.
Scope: an audit, not a blanket rewrite. For each affected catalogue under app/translations/*/LC_MESSAGES/messages.po:
Establish the settled register from the catalogue's own history — the strings that predate the Still hardcoded or missing keys for translation #340 fill (git log around commit 2132f12) are the evidence, exactly as they were for Hungarian. Do not impose a house style where the catalogue has not already chosen one.
Where the pre-Still hardcoded or missing keys for translation #340 content is too thin or genuinely mixed to establish a baseline, record that and leave it alone. That is a question for a native speaker, not for us.
Start with de, fr and es: they are the largest catalogues and the most likely to be read.
Acceptance criteria:
A written finding per catalogue: settled register, or "no baseline, left alone" with reasoning.
Corrections landed only for catalogues with an established baseline, register-only, msgid set still matching messages.pot exactly, nothing left blank or fuzzy.
A guard test in the shape of tests/test_i18n_issue_350.py for each catalogue that gets corrected, so the register cannot silently regress on the next bulk fill.
The full suite passes.
Hungarian is already done (#350) and is out of scope here.
Issue #350 found that the bulk translation fill in #340 introduced formal-register strings into the Hungarian catalogue, which had been consistently informal since well before #340. Twenty-eight msgstrs had to be rewritten in 4c14615 to put it back.
The same fill produced the other eighteen catalogues, and several of those languages draw the same T–V distinction: German (Sie/du), French (vous/tu), Spanish (usted/tú), Italian, Portuguese, Dutch, Polish, Czech, Russian among them. There is no reason to think Hungarian was uniquely affected, and we only caught it because a native speaker raised it.
Scope: an audit, not a blanket rewrite. For each affected catalogue under
app/translations/*/LC_MESSAGES/messages.po:git logaround commit 2132f12) are the evidence, exactly as they were for Hungarian. Do not impose a house style where the catalogue has not already chosen one.Start with de, fr and es: they are the largest catalogues and the most likely to be read.
Acceptance criteria:
messages.potexactly, nothing left blank or fuzzy.tests/test_i18n_issue_350.pyfor each catalogue that gets corrected, so the register cannot silently regress on the next bulk fill.Hungarian is already done (#350) and is out of scope here.