Translation is one of the most demanding topics in the wpmu dev support forum. According to the 2012 WordPress survey, two thirds of WordPress users live outside the United States. It may be a person who develops websites for many people who use English as a second language and those who do not know English at all. So today we start word press translation series. 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. In the first post, we will show you how to translate the topic 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 Before you can find a topic for a ready character, you must find the topic to translate. But you can’t translate old topics. Topics need to be localized using the GNU gettext framework. That is, you are ready to translate the topic. If the topic is not localized, please return later this week to learn how to prepare the topic translation. The
Developers do not always create topics ready for translation, so when purchasing advanced topics, make sure they are ready for translation. The WordPress topic repository contains tags for finding translation ready topics. If you only need free themes, you can easily search the WordPress Theme repository for designs ready for translation. WordPress Go to org, go to the topic, and see the new filter and tag interface. On the next page, select translation ready, and then click Find topic. After you determine the theme, open the zip file and browse the language folder. The pot file must be included. The
WordPress uses the GNU gettext localization framework for translation. The framework uses three types of files: 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. The
Mo (machine object) file: in the last step, the Po file will be converted to a machine-readable format. There are several different options for translating WordPress introduced in WordPress Codex using poedit. This tutorial will use the easy-to-use open source program poedit, which can be used on Mac OS X, windows, and unix\/linux. 1. install poedit. 2. open poedit, navigate to the new directory of file >pot file, and select pot from the language folder of the topic. The
3. the directory attribute box appears, asking for information about the content to be translated. Please enter the language to be translated here. Enter the language and other important details you want to translate, and then click OK. 4. clicking OK will prompt you to specify the name of the translation file. Names are important, and there are specific formats to follow. For example, when translating Chinese, the file name must be zh\u ch.po, and tl\u pH when translating Tagalog in the Philippines.
