The Files Used For Translating

You’ll have one pair of PO/MO files per language and region, but only one (optional) POT per domain.

PO (Portable Object) file

A list of readable “translated objects”

MO (Machine Object) file

The corresponding binary (to be interpreted by Gettext when doing localization).

POT (PO Template) file

Contains all existing keys from your source files, and can be used as a guide to generate and update all PO files.

Not mandatory. Depending on the tool you’re using to do l10n, you’ll be just fine with only PO/MO files

Creating custom language files for a child theme

A child theme always uses the translation of the parent theme. You have to use a different / the child themes text-domain slug for all translation function calls in the child theme files

Copy the .po and .mo files to: “wp-content/languages/themes”

Name them “[yourchildthemename]-nl_NL.po” and “[yourchildthemename]”

Replacing [yourchildthemename] with the name of your child theme.

UK Electronic Designer
We benefit hugely from resources on the web so we decided we should try and give back some of our knowledge and resources to the community by opening up many of our company’s internal notes and libraries through mini sites like this. We hope you find the site helpful.
Please feel free to comment if you can add help to this page or point out issues and solutions you have found, but please note that we do not provide support on this site. If you need help with a problem please use one of the many online forums.


Your email address will not be published.