test for: is the MO up-to-date?

[syphar]

this one is probably django-specific, since the discovery-settings in makemessages are.

[syphar]

we need either a local xgettext installation for this, or use a library like babel

[codingjoe]

you need xgettext anyway to use i18n

[syphar]

why?

[codingjoe]

well django needs xgettext to run compilemessages

[syphar]

Do check if the mo is up-to-date you don't need compilemessages.

It's about message discovery (makemessages) and the content of the mo

[codingjoe]

Chicken or the egg?

[syphar]

I don't understand ... ?

This issue is for catching the case that you marked strings for translation in your code, but didn't run makemessages.

What do you mean?

[codingjoe]

Ok, I though you wanted to actually compile the PO into an MO file.

What Is it you want to detect exactly? That the MO file is proper representation of PO or that it changed?

I feel, that this is over the top. We could rather extend our buildpack to compile all PO files.

[syphar]

currently we test (already):

• mo == po
• contents of the po (empty entries, fuzzy entries).

So the only step not tested is:

• does the po contain all entries marked for translation.

[syphar]

but you'll see it if you finally review the plugin ;)

[syphar]

closing for now, is more nice-to have,