.mo files are not up to date with .po files

[dracos]

For example, looking at https://github.com/pennersr/django-allauth/tree/master/allauth/locale/es/LC_MESSAGES the .po file was fixed a month ago to correct some fuzzy translations, but the mo file still dates from 0.19. This proved confusing when deploying allauth 0.21 and finding the Spanish translation of the check your email page not working (as that was one of the fuzzy translations fixed) without manually compiling a more up-to-date .mo file in our virtual environment.

[pennersr]

For 0.22.0 the mo files have been updated, though I quite dislike having to do this manually and committing binaries to the git repo. I am keeping this ticket open to investigate if it is feasible to generate the mo's from setup.py and removing them from the archive altogether.

[slav0nic]

for compiling mo i use https://github.com/slav0nic/DjangoBB/blob/master/setup.py#L9-L31

better move translation to service like transifex, outdated translation is annoying :|

[Flimm]

Of interest for probably anyone affected by this issue is that .po files are not up-to-date with code either. (Issue https://github.com/pennersr/django-allauth/issues/1259)

[juandgc]

still not up-to-date, both files, .po and .mo

[lukeburden]

Continuing on from #1721 ..

I like the simplicity of the approach of just including the MO files. It's dumb .. in the best way something can be dumb, though! It lets all install methods (even copy and pasting .. as inadvisable as that'd be!) work. It keeps the setup script as simple as possible (adding the ability to compile messages during setup.py strikes me as unnecessary complexity).

I really do get your aversion to including the files, it makes me cringe a little too, but I can't help but think any other approach is probably over-engineering. I suspect this is why most prominent Django apps, including Django itself, just include the MO files in their repositories.

[eriktelepovsky]

Please include .mo files in the repository or add compile script into setup.py. It would be really useful.

[DmytroLitvinov]

Talking about fuzzy string. Right now in the release 0.43 we have a fuzzy strings also. For example this one

[pennersr]

These days, setup.py is mostly empty and I don't think it is worth to add complexity here to somehow automatically compile .mo files. And, as stated, I really don't want to add the .mo files to the Git repo. So, we'll just have to rely on the release process to update .po / compile .mo.