Welcome to the official blog of the translators team for the WordPress open sourceOpen SourceOpen Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. project.
This is where we discuss all things related to translating WordPress. Follow our progress for general updates, status reports, and debates.
We have meetings every week and at various hours every week. Check SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. in #polyglots (the schedule is on the sidebarSidebarA sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. of this page or the meeting schedule page). You are also welcome to ask questions on the same channel at any time!
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.
To translate WordPress in your language you will need to post a request in the Polyglots Blog that a new localeLocaleLocale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/ for it be added to translate.wordpress.org.
Before you do that, please read this page carefully, follow the steps, and gather the information needed.
The Projects by language page of Translate.WordPress.orgtranslate.wordpress.orgThe platform for contributing to the translation of WordPress core, themes and plugins. lists all the localesLocaleLocale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/ that already exist and are ready for translations. If the language you’d like to translate for is there, great! You are ready to start translating after logging into your WordPress.orgWordPress.orgThe community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ account.
If the language is there, but it looks like no one is working on it, check the Inactive translations page of the Handbook for instructions.
It is, of course, possible to translate and maintain a translation on your own, but at times it will be overwhelming. The WordPress project alone has more than 4000 stringsStringA string is a translatable part of the software. A translation consists of a multitude of localized strings.. The first thing you should do is gather a team to work on your translation. Each member of your team will need a WordPress.org username. They don’t already have one, it’s easy to register for one here.
We strongly recommend that you organize a team of at least two or three other people to help out. The good news is you can usually recruit this translation team from your existing WordPress community. If you don’t yet have a local WordPress community, this is a great time to form one. Your translation team will probably form the coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. of your future community. Many teams start with the mere objective of translating WordPress and evolve into a full-fledged community, organizing meetups and sometimes even WordCamps.
It’s now time to find a language code. Keep in mind that it is indeed a language code and not a country code. The first thing you should check is the list of locales that GlotPress supports. If your language code is there, that’s the one you should be using. If not, use Wikipedia or Ethnologue to find your language and the appropriate ISO 639-1, ISO 639-2 and ISO 639-3 codes. ISO 639-1 used to be used for the language subdomains, but for new locales we now use the ISO 639-3ISO 639-3ISO 639-3 code is an international standard for language codes in the ISO 639 series. It defines three‐letter codes for identifying languages. code. In case you need more background, the Ethnologue website is a good resource.
This is only relevant if you’re planning to translate a language that varies from country to country, like French (which varies in Canada, Belgium, Switzerland, France, and many more). If such a variation exists, the country code will be appended to your subdomain, as in fr-ca for Canadian French or es-mx for Spanish as spoken in Mexico.
Example: Spanish has a lot of location-specific locales.
After you research the language and country codes, you should find out how the plural forms of your language are defined. The following information is needed:
how many plural forms there are in your language (English, for example, has two, but Japanese only has one)
Once your request is fulfilled, you will then have at your disposal a Rosetta site, such as http://fr-ca.wordpress.org and support for translating all of Translate WordPress’ projects.
All of the above will be under the control of the WordPress.org user you have specified.
Have you looked through and completed all of the steps above? Excellent! Now it’s time to request your new locale.
Go to the polyglots blog and create a new post with the following information:
Locale: The ISO 639-3 locale code that is specific for your language
Country code: The specific code for your country (e.g. es for Spain or mx for Mexico)
Plural forms: The number of plural forms and the rules for those (e.g. nplurals=2, (n>1) for Artipan)
Language native name: The name of the language in the language (e.g. Български for Bulgarian)
Language English name: The name of the language in English (e.g. Bulgarian)
Sub-domain: The subdomain of your site will use the ISO 639-3 language code, so that’s what you will need to provide. Exceptions are locales for location-specific languages, where the subdomain uses the two-letter ISO 639-2 code followed by the country code (e.g. es_mx for Mexican Spanish)
Site Title: The title for your site should be the “Country or language name”
Site Description: The phrase “WordPress in xxx language” in your native language
Admin Username(s): The wordpress.org usernames of the admins for your site
As an example, here’s the form filled in for Spanish in Mexico:
Please note it may take some time for one of polyglots teamPolyglots TeamPolyglots Team is a group of multilingual translators who work on translating plugins, themes, documentation, and front-facing marketing copy. https://make.wordpress.org/polyglots/teams/. volunteers to be assigned for your request since there currently is a backlog. You can check the progress of all pending requests on this list.
