Table of Contents
- Starting a new translation
- Translations repository
- General guidelines
- Building a glossary for your language
- Message types
- Translator comments
- Source-file references
- Translation Tools
- Gettext overview
- Gettext command-line tools
- Local sites at <locale>.wordpress.org
- Local forums at <locale>.forums.wordpress.org
- Requesting a new forum
- Translating the forums interface
- Requesting translations deploy
- Adding moderators
Starting a new translation
Why would I want to translate WordPress?
WordPress is a free software project. What this means is that everybody can contribute to it, and is encouraged to, in order for it to develop and grow. That’s why every free software project needs volunteers — people who are willing to contribute their free time to development of a particular piece of software, either by helping write code, design graphics, or… translate it. That’s where you come in.
There are numerous ways your community could benefit from your translation. The most obvious one is probably enabling people who don’t speak English at all, to use WordPress. The lack of a translation could prove to be a difficult barrier for many to pass, so a translation is necessary for them to make use of WordPress. Many people also simply prefer to have their software translated, and would grab your translation just because of that.
Every translation can have a local website, which can contain static pages, a blog, a download section, where people can download all the releases of your translation, and an automatic update feature for all WordPress sites in your language! This means that every time a new version of your translation is released, its users are offered an upgrade on the dashboards of their own websites.
If your language has a great number of WordPress users, or gains one thanks to your translation, you may find that a place to provide support is helpful. If you have been translating WordPress for some time and your translation is well established, you can request the creation of local forums. Other than helping each other, users of your translation could also exchange their views on WordPress and suggest changes that could be applied to your translation in one place hosted on the official WordPress servers.
Oh, and did I mention you get to work with a lot of great people?
As a translator, you want to make sure the language of the localized project is well polished. Establishing and following translation rules might seem like a lot of extra work if you are just starting out. In fact, it can cut the translation team’s workload by reducing the need for correction and clarification.
Keep in mind that localized content should sound natural and capture the original content’s meaning, instead of being strictly literal to the original. Try to understand the context and keep the tone consistent.
Building a Glossary
To keep your translations consistent, build and use a glossary for your language. You might want to look into these methods:
- Use Google Translation Toolkit
- Create a Codex page
- Create a public Google spreadsheet
Building a Style Guide
In addition to a glossary, style guide can help your team by keeping translations consistent and making it easy to agree on one translation. Rules to include:
- Formatting (bolding, fonts, spacing)
- Tone (formal vs. informal)
- Notes on special case / exceptions
- Branding & trademark
You may be able to find something to build upon by searching “style guide” (or “translation style guide”) in your language. These can be a good start too:
- TED.com: Style guidelines for translators
- Microsoft’s language style guide collection
- Mozilla Style Guide: Translation
Once you have a style guide, put it somewhere public, such as a Codex page or published PDF, and link it from where translators’ guide page for your language.
Local sites at <locale>.wordpress.org
Requesting a new site
So that the page is also available in your language, you can use the texts which we have inserted automatically translated and change.
Building local packages
When you are ready to build a package for testing or releasing a new version of WordPress in your language, you can use the package build tool located in your local site. The tool is located at “Tools → Translations for <locale>” (where <locale> is your locale code).
- Check in all updated files into the current branch directory.
- If you are using the GlotPress translations, make sure everything is translated. Translations are handled in three different projects: Core, Multisite, Continents & Cities and the Twenty Eleven theme.
- Copy the current branch directory and create a new tag directory under
Building a Package
- Select where you want to get your translations from (.po/.mo files under
/messagessvn folder or GlotPress).
- Locale Branch: This determines the location where your language-specific files are taken from. If you don’t see the branch/tag, you will have to create one in the SVN repository and give it a few minutes. Alternatively, you can build from the trunk for some occasions.
- WordPress Branch: This determines where rest of the files are taken from.
- WordPress Revision Number: This is used when no tag is specified as WordPress Branch above.
- WordPress Version: The version number you would like to use as a part of the package file name. It can be a version number (e.g. 3.0 or 3.0.1) or a combination of a number and type of the release (e.g. 3.0-RC1 or 3.0-beta1).
Once all options are filled out, click the “Build” button at the bottom. The tool will check for errors, and the package will show up at the top of the list on this page if it is successfully built.
Releasing new versions
After building a new package, you can share the download URL among your translation team for testing. You can find the URLs under the “Link” column on the Translations for <locale> page, in zip or tar.gz format.
If testing goes well and you’re ready to release the final version to the public, simply click the version’s “Release” link under the “Action” column. This will mark the official release of that version. Users will be prompted for upgrade of their language package on their dashboard, and download information on your locale site will be updated.
Go in the Menu to Users -> New user – and enter the user’s e-mail address in this field, and set a role.
The user roles are the same as on WordPress. In addition, you can select the Validator role for a user. Validator can validate (approve) strings on GlotPress, but doesn’t receive any additional privileges on the local site.
WordPress is great, we know. With Showcase you have the possibility to show your visitors that websites are running in your country by WordPress.Go to the Showcase Page, put a Title, URL and Excerpt to the form and click “Save”. The Showcase Picture will load automatically.