Alert: This page is still a draft and being actively written. If you find an error, please comment below.

[Information on interacting with the translation repository and all the processes involved. Some overlap with Core Contributor Handbook as needed. Also grabbing information from here.]

The WordPress Localization Repository at is a Subversion repository where official WordPress translations are maintained. Various teams collaborate on translations for their native language, and team maintainers commit updates and changes to the repository.

Participating #

Participation in the repository is open to anyone. Simply visit the WP Polyglots Blog, introduce yourself, and let everyone know what translation you’d like to work on. If there is already a team for your language and locale, they’ll let you know and you can join them. If not, you can either volunteer to be a maintainer for your language and locale, or simply contribute your localization and the repository maintainers will add it.

Top ↑

Guidelines and requirements #

Note: these guidelines are subject to change as the system evolves; repository maintainers will be happy to assist you in updating the files you maintain in the repository should these guidelines change.

Character Encodings #

All localizations should have at least a UTF-8 version, but may optionally add versions in other character encodings popular for that locale.

Current PHP versions don’t support Byte Order Markers (BOMs), so be sure the UTF-8 encoded files you contribute do not have them.

Top ↑

HTML Character Entities #

With a few exceptions (noted below), all translations should be written literally, rather than escaping accented and special characters with HTML character entities.

Some characters must be escaped to avoid conflict with XHTML markup: angle brackets (< and >), and ampersands (&). In addition, there are a few other characters better used escaped, such as non-breaking spaces ( ), angle quotes («and »), curly apostrophes () and curly quotes.

For more information about the W3C’s best practices involving character encodings and character entities, see the following references:

Top ↑

Repository File Structure #

The repository contains directories for each locale, which are named as follows:

Within each locale’s directory are the regular Subversion versioning directories: branches/, tags/, and trunk/.

Inside the appropriate versioning directory are the following subdirectories:

dist/ #

This directory contains all files in the WordPress distribution that cannot be Gettexted, which have been translated into the target locale.

If the locale has only a UTF-8 translation of the files, the dist/ directory may be populated with them directly, and the structure within dist should mirror the structure of the WordPress root directory:

  • dist/
    • license.txt
    • readme.html
    • wp-config-sample.php
    • wp-admin/