From WordPress 4.0 you’ll be able to select your native language directly from the install screen as shown below.
This makes it more important than ever to be able to translate your WordPress theme to match the language used on the rest of your site. This post explains how do to exactly that!
Are you Speaking my Language?
It goes without saying (but I’ll say it anyway) that all WPGO themes are fully translatable and include the necessary translation file(s) to get you started! 🙂
Inside the WPGO theme framework all instances of text, and labels, are wrapped inside special functions so they can be translated into any language as necessary. There is also a master translation file (a POT file) which can be found in the theme languages folder.
The translation process utilizes the the POT file shipped with the theme to create an output file with extension .po which is used to display translation phrases in your own language. Let’s do this next.
The program we will be using to translate the theme is Poedit, which is freely available for all major operating systems including Windows, OS X, and Linux. If you haven’t already done so, install Poedit now. Then open it up, and from File the menu select: New catalog from POT file…
Navigate to the languages folder and open the POT file in Poedit. You’ll see the “Catalog properties” dialog box appear. You don’t need to change any of these settings so just go ahead and click OK to close.
You will now be prompted to choose the location and filename for your .po translation file, which is used to store all your theme translations. Make sure you choose to save the .po file in the same directory as the theme POT file.
The default filename will be something like default.po. This is OK for now but you will need to change this later on to be more specific so WordPress knows which file to use for language translation.
For now just go ahead and click Save to close the “Save as…” dialog box. This will create a .po file to your theme languages folder. You may also notice that a .mo file is saved along with the .po file. Make sure that these two files are kept together.
All WPGO themes support the .po file being located in the in the parent them languages folder OR the child theme languages folder. If a child theme is active then the child theme languages folder will be checked FIRST. If no language file (that matches the locale set in WP config) is found then it looks in the parent theme languages folder. This means that you can use a custom translation file in a child theme and it won’t ever be overwritten during theme updates!
Creating the Translation Phrases
Now for the fun part! You can start to create theme translations for any phrase used in the theme in your own language! Simply click on a phrase from the list in the main window to get started.
Note: If you save your .po file in the parent theme languages folder then that’s fine but you should be aware that it will be overwritten during a theme upgrade. Prevent this by using a child theme and saving the .po file in the child theme languages folder (create one if the folder doesn’t already exist).
Towards the bottom of the Poedit screen you will see two text boxes. The first one (Source Text) is a read-only box that shows the text of the phrase you just clicked on. The second one (Translation) is where you enter your translations.
As soon as you enter your translated text in the ‘Translation’ text box you will also see it appear in the main window to the right of the original text. Also, for convenience, every translated phrase in the main window has a star added to the very left to make it easy to spot phrases that have already been translated.
When you have finished editing make sure to save your work by clicking the Save icon.
It’s important that .po (and .mo) filenames match the desired locale as specified in wp-config.php (located in your WordPress root directory). The naming convention is
Some examples of .po file names are:
Open up your WordPress wp-config.php file and add the WPLANG PHP constant, if one doesn’t already exist, as follows:
define ('WPLANG', 'en_UK');
In this example I am using the English UK locale so this would require the .po and .mo files to be named as:
The rule of thumb is that whatever your .po and .mo files are called, the WPLANG constant in wp-config.php should be exactly the same (not including the file extension).
If you want to learn more about how WordPress handles language translation then click here to find out more.
Has this document been useful to you? Please contact us if you think this document could be improved in any way. We are committed to providing the highest level of support!