[Django] #28801: Outdated translatable text of a contrib.auth literal

[Django]

#28801: Outdated translatable text of a contrib.auth literal
-------------------------------------+-------------------------------------
Reporter: Ramiro | Owner: nobody
Morales |
Type: Bug | Status: new
Component: | Version: 2.0
Internationalization | Keywords: transifex
Severity: Normal | makemessages po catalog
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
I'm routinely reviewing the es_AR translations for 2.0 and note the form
at /admin/auth/user/n/change/ shows text in English (''Raw passwords are
not stored, so there is no way to see this user's password, but you can
change the password using this form.'')

1. The text is correctly translated in the
django/contrib/auth/locale/es_AR/LC_MESSAGES/django.po file (line 70 as of
now). Original msgid there is
{{{
msgid ""
"Raw passwords are not stored, so there is no way to see this user's "
"password, but you can change the password using <a href=\"../password/"
"\">this form</a>."
}}}
2. Strangely, the modification date of both .po and .mo file is Oct 1st.
2016
3. Looking at the original Python source code, one can see the actual
literal is different from the msgid:
{{{
"Raw passwords are not stored, so there is no way to see this
"
"user's password, but you can change the password using "
"<a href=\"{}\">this form</a>."
}}}

(note the presence of a placeholder on the link at the end).

So it seems the (Transifex?) Python source code translatable literal
extraction isn't working, for this particular file?

Other translations suffer from the same issue, e.g.
[https://github.com/django/django/blob/374b6091ac5ca96d05945413f3a362cc29ec9511/django/contrib/auth/locale/fr/LC_MESSAGES/django.po#L70
French].

--
Ticket URL: <https://code.djangoproject.com/ticket/28801>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#28801: Outdated translatable text of a contrib.auth literal
-------------------------------------+-------------------------------------

Reporter: Ramiro Morales | Owner: nobody

Type: Bug | Status: new
Component: | Version: 2.0
Internationalization |

Severity: Normal | Resolution:
Keywords: transifex | Triage Stage:
makemessages po catalog | Unreviewed
Has patch: 0 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Comment (by Claude Paroz):

Hey Ramiro, this string changed between 1.11 and 2.0
[c52ae33a0c0c0bbaa460607a8787e95fe983a2b9].
Once Transifex translations for 2.0 will be fetched, I suppose the issue
will be resolved, or maybe I didn't understand this ticket?

--
Ticket URL: <https://code.djangoproject.com/ticket/28801#comment:1>

[Django]

#28801: Outdated translatable text of a contrib.auth literal
-------------------------------------+-------------------------------------

Reporter: Ramiro Morales | Owner: nobody

Type: Bug | Status: new
Component: | Version: 2.0
Internationalization |

Severity: Normal | Resolution:
Keywords: transifex | Triage Stage:
makemessages po catalog | Unreviewed

Has patch: 0 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Comment (by Ramiro Morales):

Hello Claude,

I think maybe it´s me who doesn't understand things re: our translations
workflow.

I assumed just before 2.0 RC1 was tagged there was a

{{{
Python/JS source code -┬--> django{,js}.{po,mo}
└--> Transifex
}}}
resync of the translations. And maybe a fetch of translations from
Transifex.

So I downloaded RC1 expecting to see up to date translations .

Now I'm realizing things seem to be actually OK on the Transifex side:
* Literals were extracted from the Python/JS source code
* They were pushed to Transifex (maybe using the Transifex CLI tools?)
* We translators worked on them

But the .po/.mo files on the `stable-2.0.x` branch aren't supposed to be
up to date at this point, but rather just before 2.0 final gets released.
And this is why I see incomplete translations when test driving 2.0 rc1.

So, if this is the case. Please free to disregard this ticket. And sorry
for the noise.

--
Ticket URL: <https://code.djangoproject.com/ticket/28801#comment:2>

[Django]

#28801: Outdated translatable text of a contrib.auth literal
-------------------------------------+-------------------------------------

Reporter: Ramiro Morales | Owner: nobody

Type: Bug | Status: closed
Component: | Version: 2.0
Internationalization | Resolution:
Severity: Normal | worksforme

Keywords: transifex | Triage Stage:
makemessages po catalog | Unreviewed

Has patch: 0 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Changes (by Claude Paroz):

* status: new => closed
* resolution: => worksforme

Comment:

Yes, your explanation is right.
It might be useful to fetch and include translations before the RC1, but
as we don't guarantee string freeze before RC1, the "risk" is to have to
reinclude most translations a second time before final release. And that's
a problem currently because of the size of the binary .mo files in the
repository (#23321).

--
Ticket URL: <https://code.djangoproject.com/ticket/28801#comment:3>