Outdated translatable text of a contrib.auth literal

[Ramiro Morales]

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. ​French.

[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?

[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 feel free to disregard this ticket. And sorry for the noise.

[Claude Paroz]

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).