Request support for it by following this guide. We’ll have you up and running in no time.
Weekly Meetings
We have two weekly meetings on Slack in #polyglots, on Wednesday 06:00 UTC and Wednesday 11:00 UTC. If you have any questions, bring them to the weekly chats!
Posting here
In order to post to this site, you will need to log in with your wordpress.org account. Your first post may take a while to show up, as it is moderated. Please follow our tag policy when posting.
The polyglots team is responsible translating WordPress is in hundreds of languages. It’s a big job, which is why we need help from native speakers to make it possible.
On translate.wordpress.org, you will find a list of every language available for translating WordPress. If you speak one of the languages listed and it hasn’t been completely translated (listed at 100%), you can see the untranslated strings and suggest translations.
Before your translations become part of WordPress, they will need to be approved by a translation editor – a trusted member of the polyglots community who can also appoint new translation editors.
On the official site for translating WordPress – http://translate.wordpress.org, The Polyglots team uses a WordPress plugin called GlotPress that turns WordPress into a translation management system. It allows collaborative work by translation contributors and translation editors and is the recommended tool for translating WordPress, plugins and themes.
Rosetta Sites are gateways to local communities. They are the version of WordPress.org in a specific language. They are also the place where you can download WordPress in that language, find more information on the team of translators and see examples of websites that have been built with WordPress in that language.
Local forums are the place for discussions and support in a specific language.
Internationalization and localization (commonly abbreviated as i18n and l10n respectively) are terms used to describe the effort to make WordPress (and other such projects) available in languages other than English for people from different locales, who have different dialects and local preferences.
The process of localizing software has two steps. The first step is when the developers provide a mechanism and method for the eventual translation of the program and its interface to suit local preferences and languages for users worldwide. This process is internationalization (i18n). WordPress developers have done this already, so in theory, WordPress can be used in any language.
The second step is the actual localization (l10n), the process by which the text on the page and other settings are translated and adapted to another language and culture, using the framework prescribed by the developers of the software. WordPress has already been localized into many languages (see our list of teams for more information).
This handbook explains how translators (bi- or multi-lingual WordPress users) can go about localizing WordPress to more languages.
Throughout this handbook, we’ll use a few terms that you might want to familiarize yourself with.
Internationalization: As mentioned above, internationalization is the method in which we make WordPress available in different languages and regions.
Localization: Localization is the process of translating software to a different language. This term is often used interchangeably in this handbook with internationalization.
Locale: A locale (as opposed to “local”) is the combination of a language and a regional dialect. Locales often refer to countries. For example, Portuguese (Portugal) and Portuguese (Brazilian). The default locale for WordPress is English (U.S.). To define a locale we either use a language code + a country code or the ISO 639-3 code of a language.
Rosetta site: The local WordPress.org site for a specific locale. For example the Portuguese Rosetta site is pt.wordpress.org and the Bulgarian site is bg.wordpress.org.
