...
Please note that for core Revive Adserver plugins, the generation of the binary .mo files is handled by the Crowdin project; so, similar to the way the core product translations are handled, it is only necessary to edit the required English language .po file(s) for the plugin in the master branch, and the changes will be automatically uploaded to Crowdin, translated by the community, and the updates made there will be periodically merged by the core Revive Adserver team into the master branch's core plugin .mo files, and will be included in the next release.
Editing .po Files
...
The Revive Adserver code team uses poedit to edit the master English .po files.
3rd Party Plugins / Core Plugin Development
...
As a result, it may be necessary for developers to generate the .mo files for plugins manually - either because they will need to generate them to include as part of their 3rd party plugin, or so that they can simply see the proposed changes to .po files in a development environment.
Generating .mo Files
To generate a .mo file, the gettext msgfmt utility. For example:
| Code Block |
|---|
cd plugins_repo/openxDeliveryLimitations/plugins/etc/Site/_lang
msgfmt -o en.mo po/en.po |
This will re-create the en.mo file, based on the en.po file, for the Site component of the plugin in the openxDeliveryLimitations directoryAn updated .mo file can be generated from the .po file using poedit.
| Note |
|---|
For core Revive Adserver plugins, do NOT commit changed .mo files to the repository. See above for how .mo files are managed using Crowdin. |