Software >> WordPress

• WordPress' official site
• WordPress on Wikipedia
• WordPress' Pootle page at Locamotion.org

On the Pootle server you'll find 12 different files to translate, even though WordPress officially has only one POT file. An explanation of the 12 files, and how to deal with them if you're a translator leader, can be found here.

• Customised Google search for WordPress terminology
• WordPress glossary for Pootle

WordPress is a blogging system. The company offers free hosting, but it can be installed on a user's own web site easily, if he has a host with PHP/MySQL enabled.

Author: List of developers here

Being translated. The language file of WordPress on Pootle was uploaded in June 2008, but may not be the absolute latest version. Please continue to translate the version currently in Pootle.

* Which version is the latest version of WordPress? See here..

If your English isn't that good, and you wish to translate from another language, or if you want to use a second language as a reference while translating, our Pootle server has the second-language feature enabled. You can view the Arabic, German, Spanish, French, Japanese, Continental Portuguese, Russian and Simplified Chinese strings while you translate from English.

These eight languages are available on the server in read-only format. If you want to help translate them, contact their official translators.

To activate a second source language in Pootle, go to your profile page and select the second language under Alternative Source Language.

• Total number of strings: 2219
• Total number of words: 12749
• Original file format: Gettext PO

The above information is for the official wordpress.pot file. However, there are additional texts to be translated (an additional 1665 words), as well as a default theme, which is not included here.

Already translated into about 40 languages. Decathlon translators can translate into any language, if they attempt to get cooperation from existing translator, where available.

• Overview of WordPress translation process
• List of languages already translated (and their teams)
• Another list of languages already translated (differs from the first list)
• An additional list of language teams (overlaps previous two lists)
• Additional files to be translated

The source text may contain HTML entities such as ’. You don't need to include these in your translation. The example entity here is actually a single quote. If you need to use a single quote in your translation, there is also no need to use the entity code -- you can simply type a single quote, as normal.

Another example is “ and ”. These two are actually curly quote characters. You don't need to use curly quotes in your translations -- straight quotes, typed as-is, are quite acceptable.

— is an em dash.

… is an ellips (three dots). Feel free to translate it with three literal dots (…) instead of a single character.

« (left angle quote) and » (right angle quote) may be translated as-is, or replaced with < (<)and > (>).

Some strings contain inline comments. This means that there is a helpful comment inside the source text string. Do not translate the comment. For example:

", |between list items"
", and |between last two list items"
" and |between only two list items"

would be translated into Afrikaans as:

", "
", en "
" en "

You may encounter something like Y/m/d g:i:s A in the translation. This is a code for date and time formats. In your translation, type the code for the date format used in your language.

More information on the PHP date/time format:

• http://codex.wordpress.org/Formatting_Date_and_Time
• http://php.net/date

If you encounter PHP codes within the source text, keep it as-is, and write a short explanation next to it if you think folks in your language won't know what it means.

For example:

• Source: Your php.ini upload_max_filesize is %s.
• Translation: Jou php.ini se upload_max_filesize (maks grootte van oplaailêer) is %s.

The bug reporting system used by Wordpress is called Trac. To report a bug, first register on the forums and then log in using the same username/password.

Bugs submitted:

• Messages in POT with date codes should refer translators to explanatory page
• Inline comments in POT should be in msgctxt instead
• Multiple entity codes in POT file for the same character
• Comments in POT file should ideally explain meaning of character entities
• Four messages in POT still have incorrect plurals

Translators' names and e-mail addresses are usually included in the translated files automatically. We also believe that translators should be given credit for their translations.

The following information was accurate in mid September 2008 (we don't keep statistics automatically). The line counts below give an approximate indication of the number of strings/messages translated.

Hindi (hi)
Jai Pandya, jaipandya[at]gmail[dot]com, Aug, 219 lines

Latvian (lv)
Imants, imantsgi[at]gmail[dot]com, Jul/Aug/Sep, 1047 lines
Ansis J Stabingis, ansis[dot]stabingis[at]gmail[dot]com, Aug, 463 lines

Norwegian (Nynorsk) (nn)
Simon Hansen, simonboba[at]gmail[dot]com, Sep, 1529 lines
Odin Omdal Hørthe, odin[dot]omdal[at]gmail[dot]com, Sep, 83 lines

Romanian (ro)
Stas Sushkov, stas[at]nerd[dot]ro, Jul/Sep, 115 lines
Codrin H, bl[dot]ueyez[at]yahoo[dot]com, Sep, 18 lines

Sundanese (su)
Dadan Nasrullah, de[dot]nasrul[at]gmail[dot]com, Jun/Jul, 1000 lines
Ki Santri, kang-hilman[at]plasa[dot]com, Jul, 537 lines
Sukma, sukma[dot]gemala[at]gmail[dot]com, a few lines

Venda (ve)
Singo Thivhusiwi, singo[at]webmail[dot]co[dot]za, Jun, 116 lines

Vietnamese (vi)
Clytie Siddall, clytie[at]riverland[dot]net[dot]au, Jun/Jul, 686 lines
Kien Nguyen, fairylandme[at]gmail[dot]com, Sep, 34 lines