Translating a ClassicPress plugin with Poedit: Create Translations

ClassicPress PluginsThis post is part of the sub-series on Translating a ClassicPress plugin with Poedit which is part of the Translating a ClassicPress plugin with Poedit series.

With a translation template created, people can now use it to translate into other languages, which is what I am going to cover in this post.

Launch Poedit and click on the large Create new translation button on the main screen:

Poedit

Select the catalogue template to open (the pot file) and click Open:

Open catalogue template

Select the language of the translation you’re going to make (I am translating my English (United States) into English (United Kingdom)) and click OK:

Translation Language

The translation window will be displayed which is broken into three sections:

  1. Source/Translation Text
  2. Source Text
  3. Translation
Poedit translation screen

To translate a string, select it in the top section, the original is shown in the middle and you type the translated text in the bottom; simply work down the list of strings entering the new text:

Translating the strings

When all strings have been converted (or if you’re taking a break), clikc the Save button on the toolbar and choose a name for your translation:

This should be named as the plugin slug_language.po; for example, url-shortener_en_GB.po.

With this done the translation file is ready for use; if you’re translating someone elses plugin, they’ll usually accept translations with thanks and include them for distribution.

Translating a ClassicPress plugin

Translating a ClassicPress plugin
What is Internationalization and Localization?
Why is Internationalization and Localization important?
When should a plugin be internationalized?
Internationalizing a ClassicPress plugin: How does internationalization work?
Internationalizing a ClassicPress plugin: What is a Text Domain and how is it specified?
Internationalizing a ClassicPress plugin: Localization functions
Internationalizing a ClassicPress plugin: Which localization functions to use?
Internationalizing a ClassicPress plugin: Localizing a string
Internationalizing a ClassicPress plugin: Don't paramaterize your text domain
Internationalizing a ClassicPress plugin: Localizing a string containing a parameter
Internationalizing a ClassicPress plugin: Localizing a string including plurals
Internationalizing a ClassicPress plugin: Localizing a string including notes for the translator
Internationalizing a ClassicPress plugin: Don't include HTML markup in localization
Internationalizing a ClassicPress plugin: Don't localize URLs
Internationalizing a ClassicPress plugin: Localizing a string including line breaks
Internationalizing a ClassicPress plugin: Load plugin translations
Translating a ClassicPress plugin with Poedit: What is Poedit?
Translating a ClassicPress plugin with Poedit: Download Poedit
Translating a ClassicPress plugin with Poedit: Install Poedit
Translating a ClassicPress plugin with Poedit: Create New Translation Template
Translating a ClassicPress plugin with Poedit: Create Translations
Translating a ClassicPress plugin with GlotPress: What is GlotPress?
Translating a ClassicPress plugin with GlotPress: Download and install GlotPress
Translating a ClassicPress plugin with GlotPress: Creating administrators
Translating a ClassicPress plugin with GlotPress: Create a project
Translating a ClassicPress plugin with GlotPress: Import translation template
Translating a ClassicPress plugin with GlotPress: Import translations
Translating a ClassicPress plugin with GlotPress: Create new translation set
Translating a ClassicPress plugin with GlotPress: Export translations
Translating a ClassicPress plugin with Poedit
What is Poedit?
Download Poedit
Install Poedit
Create New Translation Template
Create Translations

What should we write about next?





Your Name (required) –
Your Email (required) –

Leave a Reply

Your email address will not be published. Required fields are marked *