The Manual

« Section 4 »

4.1 General Overview

Each GlotPress page is comprised of four primary area’s: 1. top bar 2. breadcrumbs 3. content 4. footer

The top bar provides the primary links for GlotPress, the first three items are to the left, the final two are on the right of the bar: 1. GlotPress (home link) 2. Projects (the projects page, same as home link) 3. Locales (the locale list) 4. Profile (your GlotPress profile) 5. Logout (logout of WordPress/GlotPress).

The breadcrumbs provides a linked list of pages above where you are now for easy navigation between different parts of a project.

The content is the main content of the page you are on and varies as such.

The footer provides a clean break to the bottom of the page.

GlotPress has several high level components:

  • Users
  • Projects and Sub-Projects
  • Translation Sets
  • Original Strings
  • Translation Strings
  • Glossaries
  • Locales

A project is made up of sub-projects, translation sets, strings and glossaries.

Locales are the language and other details for a translation and are global to all parts of GlotPress.

To use GlotPress you first create a new project (or sub-project), this usually matches your program name. For example, if you were translating a WordPress plugin, like “Hello Dolly”, then you might call your GlotPress project “Hello Dolly”.

You then might create two sub projects, one for development and one for your current stable release.

Once you have the project created you then import your original strings. These are the strings that will be translated. You must extract these strings from your source code and add them to GlotPress, otherwise there will be nothing for your translators to do. If your using the WordPress plugin directory to host your source code you can extract the original strings from your plugins admin menu with the “Generate POT File” option. You can then import this POT file in to GlotPress (note a POT file is the same as a PO file).

Now you have a project and some strings to translate, you have to decide which locales to translate them in to. From the Project details, you can create new translation sets, each translation set represents a different language and regional settings that will be used during the translation.

Finally, you can select a translation set and start translating strings.

Once you have finished translating all the strings in a set you can then export the translated strings out to different resource file types to be used in your application.

Glossaries are an advanced topic that will be discussed later.