[Django] #33956: timesince filter localization doesn't work for ru-RU
Django
-------------------------------------+-------------------------------------
Reporter: | Owner: nobody
semenfilippov |
Type: Bug | Status: new
Component: | Version: 4.1
Internationalization | Keywords: timesince,
Severity: Normal | datetime, localization,
Triage Stage: | internationalization
Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Despite datetime objects being 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.
--
Ticket URL: <https://code.djangoproject.com/ticket/33956>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
-------------------------------------+-------------------------------------
Type: Bug | Status: new
Component: | Version: 4.1
Internationalization |
Keywords: timesince, | Triage Stage:
datetime, localization, | Unreviewed
internationalization |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
* Attachment "mre.zip" added.
MRE project
Django
-------------------------------------+-------------------------------------
Reporter: Semen Filippov | Owner: nobody
Type: Bug | Status: new
Component: | Version: 4.1
Internationalization |
Severity: Normal | Resolution:
Keywords: timesince, | Triage Stage:
datetime, localization, | Unreviewed
internationalization |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Old description:
> Despite datetime objects being 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.
New description:
Despite datetime objects being 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.
[https://github.com/django/django/commit/e4430f22c8e3d29ce5d9d0263fba57121938d06d
This commit] seems to introduce this bug.
--
--
Ticket URL: <https://code.djangoproject.com/ticket/33956#comment:1>
Django
-------------------------------------+-------------------------------------
Reporter: Semen Filippov | Owner: nobody
Type: Bug | Status: new
Component: | Version: 4.1
Internationalization |
Severity: Normal | Resolution:
Keywords: timesince, | Triage Stage:
datetime, localization, | Unreviewed
internationalization |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Description changed by Semen Filippov:
Old description:
> Despite datetime objects being 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.
> [https://github.com/django/django/commit/e4430f22c8e3d29ce5d9d0263fba57121938d06d
> This commit] seems to introduce this bug.
New description:
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.
[https://github.com/django/django/commit/e4430f22c8e3d29ce5d9d0263fba57121938d06d
This commit] seems to introduce this bug.
--
--
Ticket URL: <https://code.djangoproject.com/ticket/33956#comment:2>
Django
-------------------------------------+-------------------------------------
Reporter: Semen Filippov | Owner: nobody
Type: Bug | Status: new
Component: | Version: 4.1
Internationalization |
Severity: Normal | Resolution:
datetime, localization, |
internationalization |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
* stage: Unreviewed => Accepted
--
Ticket URL: <https://code.djangoproject.com/ticket/33956#comment:3>
Django
-------------------------------------+-------------------------------------
Reporter: Semen Filippov | Owner: nobody
Type: Bug | Status: new
Component: | Version: 4.1
Internationalization |
Severity: Normal | Resolution:
Keywords: timesince, | Triage Stage:
internationalization |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
* stage: Accepted => Unreviewed
Comment:
Please don't accept your own tickets.
--
Ticket URL: <https://code.djangoproject.com/ticket/33956#comment:4>
Django
-------------------------------------+-------------------------------------
Reporter: Semen Filippov | Owner: nobody
Component: | Version: 4.1
Internationalization |
Severity: Normal | Resolution: invalid
Keywords: timesince, | Triage Stage:
datetime, localization, | Unreviewed
internationalization |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => invalid
Comment:
Thanks for the report, however, translations are handled at
[https://docs.djangoproject.com/en/dev/internals/contributing/localizing/#translations.
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.
--
Ticket URL: <https://code.djangoproject.com/ticket/33956#comment:5>
Django
-------------------------------------+-------------------------------------
Reporter: Semen Filippov | Owner: nobody
Type: Bug | Status: closed
Component: | Version: 4.1
Internationalization |
Severity: Normal | Resolution: invalid
Keywords: timesince, | Triage Stage:
datetime, localization, | Unreviewed
internationalization |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Semen Filippov):
Replying to [comment:4 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.
--
Ticket URL: <https://code.djangoproject.com/ticket/33956#comment:6>