“Plural-Forms: nplurals=2 plural=(n != 1) ” “Content-Type: text/plain charset=UTF-8 ” POT files usually look something like this: This includes all of the strings of the plugin or theme in a format that’s easy to read and translate into individual PO files. When you see plugins and themes that boast they’re ‘translation ready’, it means they include a Portable Object Template (POT) file.

If you miss any text, your website will display the information in its original language, which you obviously want to avoid. This file includes every single translated string. Usually, the WordPress translation process starts with a PO file for each language you want to add. they can be read by WordPress) and are generated from PO files.

Machine Object (MO) files: These translation files are machine-readable (i.e.

Portable Object (PO) files: You need a unique PO file for each language you add to your site, and includes manual translations.

WordPress uses dedicated language files to store translations of your site’s content (or strings of text) in other languages. In practice, if you want a multilingual website, you need to translate all of your site’s components and use specific files to store the information. Translating a website is almost never as simple as opening an HTML file and changing the text within.

Let’s get to it! An Introduction to WordPress Translation We’re going to show you how Poedit WordPress translations work, and also discuss some alternatives. In this article, we’re going to talk about WordPress translation in general, then introduce the Poedit tool. This applies whether you want to translate plugins and themes as well as your site’s content.

Without the right tools, you won’t even be able to access the files and content that you want to translate.įortunately, there are a lot of options when it comes to tools for translating WordPress. Translating a WordPress website (and its associated plugins and themes) involves a lot of work.

Poedit how to use without pro version