#33956 closed Bug (invalid)
timesince filter localization doesn't work for ru-RU
| Reported by: | Semen Filippov | Owned by: | nobody |
|---|---|---|---|
| Component: | Internationalization | Version: | 4.1 |
| Severity: | Normal | Keywords: | timesince, datetime, localization, internationalization |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description (last modified by )
Despite datetime objects are translated as expected, when using timesince filter with ru-RU locale, default (en) translation is rendered. However, this is not the case with other locales I tested (de, fr, ko). Also, this issue is not present in earlier Django versions (the one I tested is 2.2). I've checked .po file for ru-RU, it seems to have all translations required.
This commit seems to introduce this bug.
Attachments (1)
Change History (7)
by , 2 years ago
comment:1 by , 2 years ago
| Description: | modified (diff) |
|---|
comment:2 by , 2 years ago
| Description: | modified (diff) |
|---|
comment:3 by , 2 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
follow-up: 6 comment:4 by , 2 years ago
| Triage Stage: | Accepted → Unreviewed |
|---|
Please don't accept your own tickets.
comment:5 by , 2 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Thanks for the report, however, translations are handled at Transifex and not in this tracker.
I've checked .po file for ru-RU, it seems to have all translations required.
We've changed the format to the %(num)d, so ru translation should be updated at Transifex.
comment:6 by , 2 years ago
Replying to Mariusz Felisiak:
Please don't accept your own tickets.
Yeah, I apologize, this is actually my first reported issue ever. Should’ve guessed this is wrong.
MRE project