Languages

GlotPress

GlotPress is a tool to help translators collaborate. Anyone can help translate WordPress.com using our GlotPress translation engine. We greatly appreciate your time and efforts in helping make WordPress.com available in other languages!

To learn more about how WordPress.com translation works, check out the Translation FAQ.

Getting Started

You will need a WordPress.com account to use GlotPress here at WordPress.com.

Once you are logged in, click “WordPress.com” under Projects.

Then click on the language you would like to translate into.

You can suggest a new translation for any of the English original strings, seen on the left. Use the Filter / Sort / Random Untranslated links to find any particular strings for which you wish to add suggestions. You may want to suggest an improvement to an existing translation, or translate a previously untranslated string.

↑ Table of Contents ↑

Add a Suggestion

Click anywhere on the table row to open a form. Type in your translation, then click “Suggest new translation →” button. Suggested strings are indicated in yellow until they are approved by a validator.

↑ Table of Contents ↑

Approval Process

A validator will review your suggestions, then approve, edit or reject them. You’ll see your translation on WordPress.com after it’s been through this approval process, and then deployed by WordPress.com staff (usually once there are about 200 newly updated strings for your language).

↑ Table of Contents ↑

Color Key

  • A Green background indicates an approved string (which may not necessarily yet be live on WordPress.com). These are the only strings that will be deployed.
  • A Yellow background indicates a string that was suggested, but not yet approved.
  • A Pink background indicates a string that was obsoleted by a newer, approved translation.
  • A Red background indicates a string that was rejected by a validator (because it was empty or incorrect).
  • An Orange background indicates a “fuzzy” string. It could be a translation suggested based on a similar string or Google Translate suggestion. Those translations need to be reviewed for accuracy and edited or approved.
  • Any string  starting with a red bar indicates that there are validation warnings. Triggers for warnings can be mismatched HTML tags or too big a difference between the length of the original and the translation. These translations need to be either corrected or their warnings explicitly discarded by validators.

↑ Table of Contents ↑

Priority

  • GlotPress interface indicates string priority order:
  • High priority (↑) : strings associated with the new features or more visible interface elements.
  • Normal (no special symbol): majority of the strings fall in this category.
  • Low priority (↓): string that are less visible or important
  • Hidden (×): strings not displayed to regular users.

Best practice is to translate strings in the order or priority. Validators should note that hidden strings are included in .po export files. When viewing an export file in Poedit, for example, you will see the strings in the same order of priority as they are in GlotPress (although you won’t see the special symbols). If you are translating in Poedit and them importing your strings into GlotPress, be sure to translate high priority strings (in the beginning of the file) first. We all want your translations to be visible and useful for as many users as possible!

↑ Table of Contents ↑

Translators vs. Validators

Any WordPress.com user (that would be you!) can suggest new translations, and we are very grateful for everyone’s help. Once a new string is entered into the GlotPress, it has the yellow “suggested” status until reviewed by a validator.

Validators have more admin rights than a contributing translator and can approve, edit, or reject translations. Only approved translations without warnings will be deployed on WordPress.com. Validators can also upload external files (typically, but not only, the .org translations) and discard warnings. A string translated by a validator is automatically approved (but will still generate all applicable warnings).

There is no technical limit on how many users can be validators, however, translation communities should only have a couple of validators in order to have clear leadership and to minimize potential disputes.

We strongly encourage all translators (particularly validators) to get in touch with their respective .org translation community, so that consistency can be maintained across versions.

If you need help or have any questions, feel free to bring them to the Translations Forum or contact support. If you would like to help validating strings for your language, submit your request via the Translations Forum.

Still confused?

Contact support.

Not quite what you're looking for?

Get Help