Opened 3 weeks ago
Closed 3 weeks ago
#37189 closed Bug (invalid)
Dutch translation for MinimumLengthValidator error message is incorrect
| Reported by: | Bart Dikmans | Owned by: | |
|---|---|---|---|
| Component: | contrib.auth | Version: | 5.2 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
The MinimumLengthValidator for the dutch (nl) language is not correctly translating the message. This happens due to the contrib-> auth -> locale -> nl django.po file containing old values.
I compared the Dutch one to other versions the change seems simple:
Dutch version:
msgid ""
"This password is too short. It must contain at least %(min_length)d "
"character."
msgid_plural ""
"This password is too short. It must contain at least %(min_length)d "
"characters."
English/Spanish/German version:
msgid "This password is too short. It must contain at least %d character."
msgid_plural ""
"This password is too short. It must contain at least %d characters."
Should be a quick fix for anyone with permission to the translation files
Change History (1)
comment:1 by , 3 weeks ago
| Easy pickings: | unset |
|---|---|
| Resolution: | → invalid |
| Status: | new → closed |
Thanks for pointing out the discrepancy. To fix this, we're going to need a volunteer to enter a translation for the new, adjusted string (that uses
%drather than%(min_length)d) on transifex. Notice no Dutch translation exists for it. I take the point that we just need to copy the old translation over.If someone can resolve it by August 1, it will make it into 6.1.
Then, as to why the .po file still has the old string, it looks like recent practice has been to fetch translations with a
--sinceflag to only fetch recent updates, and it's possible that these were fetched recently in a way that missed that update. When I fetch without the--sinceflag I get the correct deletion of the old strings:I'll keep that in mind when fetching translations for 6.1 final to fetch without the
--sinceflag, which I was kind of planning to do anyway for completeness given the recent process changes in this area, e.g. #37020.Resolving as invalid since it's tracked on Transifex and not here (we don't have an "informative" flag).