New Locale & Rosetta Deployment

This is the process that the Polyglots leadership team follows to add new locales, Rosetta sites and forums to the Global Network. 

Adding a New locale Adding a New locale


 

1. New Locale Request requirements 1. New Locale Request requirements

Every new locale request should consist of the following information. This information should be provided by the person requesting the locale as explained in the handbook page “Requesting a new locale

  • Locale: The ISO 639-3 locale code that is specific for your language
  • Country code: The specific code for your country (ex: es for Spain or mx for Mexico)
  • Plural forms: The number of plural forms and the rules for those (ex: nplurals=2, (n>1) for Artipan)
  • Language native name: The name of the language in the language (Ex: Български for 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 (Ex. es_mx for Mexican Spanish).
  • Site Title: The title for your site should be the “Country or language name.”
  • Site Description: A tagline or description of your site in your native language
  • Admin Username(s): The wordpress.org usernames of the admins for your site.

=================================================================

EX.

1
2
3
4
5
6
7
8
$ceb = new GP_Locale();
$ceb->english_name = 'Cebuano';
$ceb->native_name = 'Cebuano';
$ceb->lang_code_iso_639_2 = 'ceb';
$ceb->lang_code_iso_639_3 = 'ceb';
$ceb->country_code = 'ph';
$ceb->wp_locale = 'ceb';
$ceb->slug = 'ceb';

NB! Guidelines for WP Locale

Top ↑

2. Locale Research 2. Locale Research

Top ↑

3. Add New Locale to the list of GlotPress locales 3. Add New Locale to the list of GlotPress locales

Top ↑

4. Update pinned external revision of GlotPress 4. Update pinned external revision of GlotPress

(WordPress.org is pinned to a certain GlotPress version)

Top ↑

5. Add new directory in i18n.svn.wordpress.org 5. Add new directory in i18n.svn.wordpress.org

  • The name of the new directory should be the value of the wp_locale
  • Give new validators commit access to their own repositories to i18n.svn.wordpress.org

Some locales need to overwrite core files or add core files. These files can be found in the dist directory of every locale.

Top ↑

6. Deploy the GlotPress changes to all WordPress.org servers 6. Deploy the GlotPress changes to all WordPress.org servers

Top ↑

7. Create new Rosetta site 7. Create new Rosetta site

Only Super Admins can create sites on Global.WordPress.org

  • Go To Sites > Create new site
  • The site’s description is the language name in that language
  • Add subdomain (slug – matches the locale code)
  • Add Locale Associations
  • In the new Rosetta site > Add new users – Editors and General Translation Editors for the new locale
  • Give new General Translation Editors commit access to their own repositories to i18n.svn.wordpress.org
  • Set up email forwarding
  • Create a support forum for the site
  • Create an O2 for the site

Top ↑

8. Create translation sets for projects for the new locale 8. Create translation sets for projects for the new locale

Only Super Admins can create projects on translate.wordpress.org

Following these steps, super admins can create translation sets for each project needed for the new locale:

  • Go to: Translate.WordPress.org
  • Select Project
  • Select version
  • Project actions
  • New translation set
  • Choose new locale from the dropdown menu

Top ↑

9. Onboard new GTE 9. Onboard new GTE

  • Send link to Handbook – General Expectations
  • Send link to newly created project
  • Explain which projects are included in the language packs
  • Check/remind them they need a full WordPress.org profile and to register on Slack
  • Ask them to subscribe for notifications for their locale (notifications for #[locale-code], (https://profiles.wordpress.org/profile/notifications/)
  • Send information about the Polyglots weekly chat