To translate WordPress in your language you will need to post a request in the Polyglots P2 that a new localeLocale Locale = 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.
Prerequisites
Check if the locale you are about to request isn’t already there
The Projects by language page of Translate.WordPress.orgtranslate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins. lists all the localesLocale Locale = 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.org The 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.
If the locale is not in that list, read on.
Gather your team
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 stringsString A 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.
How big should your team be?
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 coreCore Core 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.
Find your language code
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-3 ISO 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.
Choose a country code
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.