If you have never translated the WordPress plug-in before, if English is a second language, or if you are a multi-national language with translation ability, it is easier than you think, and the time will not be too long. This is the fifth post in the series on WordPress translation. In the next week, we will post new posts every day to translate all aspects of WordPress. If you have any requirements, please let me know with the message below. Earlier this week, we looked at how to localize the WordPress plug-in to prepare for translation. This post will show you how to translate plug-ins ready for translation. The
This post is part of the translation weekly series. Methods for translating WordPress Themes localization and translation preparation methods for WordPress Themes set the methods for WordPress backend localization and translation preparation methods for WordPress plug-ins in your language now you can jointly translate the translation methods for WordPress plug-ins for wpmu dev products the first 6 translation plug-in numbers of the WordPress website Find plug-ins ready for roles before you start translating plug-ins, you must find the plug-ins ready for translation. This means that the strings in the plug-in code have been localized using the GNU gettext framework. The
For a complete description of the plug-in translation preparation method, please check the WordPress plug-in localization and the method to complete the translation preparation. Developers do not always create themes ready for translation. Therefore, when purchasing advanced themes, please check the function list of the plug-in or ask the developer whether the plug-in is localized. Unfortunately, the WordPress plug-in repository cannot retrieve localized plug-ins, so if you a free plug-in, you’d better check the feature list of the plug-in to determine whether it is ready for translation, or ask the developer for details. WordPress uses the GNU gettext localization framework for translation. The framework uses three types of files: The
Pot (portable object template) file: the first step in the translation process is to use the program to search the word press source code, select the text passed to the \u() or \u e() function, and generate a pot file. This file contains all the text available for translation. Po (portable object) file: Step 2: translate the text in the pot file into the target language, and save both English and translator messages in the Po file. Mo (machine object) file: in the last step, the Po file will be converted to a machine-readable format. The
You can use poedit to translate many translation tools such as globpress, launchpad and potle, but we will use poedit. Poedit is a free, open source program that can be easily used on Mac OS X, windows, and unix\/linux to edit Po files and generate Mo files. This tutorial translates the plug-in marketpress ecommerce into French. If you don’t know, all wpmu dev plug-ins are ready for translation. Let’s look at these steps. The
1. install poedit. 2. open poedit and move from the file >pot file to the new directory. 3. the directory attribute box appears, asking for information about the content to be translated. Enter the language and other details to translate here. In this window, enter the details of the translation project. Don’t forget to include language. 4. clicking OK will prompt you to specify the name of the translation file. The name is important because there are specific formats to follow for consistency. For example, if you translate Chinese, the file must be \
