Should I check in *.mo translation files into my version control system?
This is a general question. But in particular I'm working on Django projects with git repositories.
Binary data file that contains object data referenced by a program; typically used to translate program code; may be loaded or imported into the GNU gettext program. Since MO files are binary in nature, they are not human readable like . PO files.
Simply double click a file to launch it instantly in Poedit. Because POT, . PO and . MO files are standard translation and language files, the Poedit software automatically lists the original string along with the translation.
The general answer is:
if you do need those files to compile or to deploy (in shot: to "work" with) your component (set of files queried from your VCS), then yes, they should be stored in it (here: in Git).
This is the same for other kind of files (like project files for instance)
.mo files are particular:
django-admin.py compilemessages utility.
This tool runs over all available .po files and creates .mo files, which are binary files optimized for use by gettext
Meaning:
So the specific answer is not so clear-cut:
The general answer is to not store generated contents in version control.
You can include it in tarball, if it requires rare tools, or even have separate repository or disconnected branch with only those generated files (like 'html' and 'man' branches in git.git repository).
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With