How to make a Wordpress TemplateCreating a Wordpress Template
Wordpress Themes Make Prepared Translations
Internationalisation and localisation (generally shortened as ir18n or l10n) are words that describe the efforts required to make WordPress (and other such projects) available in non-English language for different language speakers with different regionalisms, different vernaculars, and different language skills. First, if the developer provides a final translating process and methodology for the application and its interfaces to meet the needs of the global user's language and preference, the application will be translated.
The WordPress developer has already done this so that WordPress can theoretically be used in any application as well. And the second stage is the localisation itself (l10n), the translation of the text on the page and other adjustments and adaptation to a different linguistic and cultural environment, using the frameworks provided by the developer of the application.
WorldPress has already been localised into many different tongues. First, we look at the kinds of data we will be working with so that we can see what to consider when localising a topic. Wordprocess uses the GNU get-text locale system for translations and there are three kinds of file used in the framework:
the POT (Portable Object Template) files: So the first stage in the compilation is to use a tool to look through the WordPress sources to find text to pass to a __() or __e() command and create a POT for it. Contains all the text available for translating. the PO (Portable Object) files:
In the second stage, you translate the text in a POT document into the destination text and save both English and translation reports in a POT document. In all respects, POT data records are the same as POT data records, except for their use. The MO (Machine Object) files: The last stage is to convert the order data into a machine-readable form.
This makes speech data much more mobile, modulary and legible. Your text domains should correspond to the slot of your Wordpress topics, which is usually the name of the directory in which they are located. First place you need to view your text domains is the first comments area of your Wordpress topics.
It is used to specify fundamental features of your plug-in, such as authors name, plug-in name, topic tag and so on. Be sure to also insert a Text Domain attribute. Here is the comments bloc of Twenty Fifteen in his own personal format. bss-files. To prepare your Wordpress topics for translation, you must incorporate the following feature into the features of your topic. Php-Datei. load_theme_textdomain('yourtheme', Templatepath. Get your Wordpress topics ready for translation.
Languages'); modify "yourtheme" to the name of your topic and "templatepath" to the place in your Wordpress topic file where you want to store your translations. It would be a good idea to create a "Languages" file in your topic tree and store your work there. And the next stage is to edit the text elements in each of your topic file and convert them into features to make them translateable.
After your topic executables are finished, the next stage is to generate a PHOT-list. Often topic writers produce and deliver PHOT documents along with Wordpress topics, so the translator can use Poedit to compile them. We use Poedit for this tutorial, an easy-to-use opensource program available for Mac OSX, Windows, and UNIX/Linux.
Get Poedit installed. Go to Poedit and go to Document > New Catalog. Enter your project's information on the Translations Property page in the Catalog Properties dialog box. Here we need to specify the function we used to locate the text in our __() and _e() topic definitions. When you click OK, you will be prompted to name and store your POT image.
Poedit will want to store your Poedit as a . pos files by default, but since the two files are the same, you can work around this by just saving the Poo as a . pos files. Rename your filename to your design, give it a pots expansion and store it in a Languages Folder in your Topics list.
If you click OK, Poedit scans the folder you specified on the Source Path page and lists the located text in the design data in your design for you. Final stage - store your POT data. Your topic is now ripe for translating! When you want to have your topic translated, see the Translating ready-to-translate WordPress topics page.