Let me share some issues about 4.0 language…

Welcome to the official blog of the translator team for the WordPress open sourceOpen Source Open 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’d love for you to help out!

Translate WordPress

You can help translate WordPress to your language by logging in to the translation platform with 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 and suggesting translations (more details).

Want to help in managing and validating translations? Get in touch with the existing language team and follow the glossaries & style guides if the team has them.

Don’t see your language? You can request support for it.

Weekly Meetings

We have meetings every week on SlackSlack Slack 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 sidebarSidebar A 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). 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.

#polyglots

Let me share some issues about 4.0 language switching functionality.

Current implementation for 4.0, adding new languages is not automatic. To get a new language to show up in the language switcher in the admin area, users have to manually copy language files to wp-content/languages directory. For example, if an initial installation is made as English (United States) and later the user wants to switch to other 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/ (his/her native 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/, etc), the user have to obtain the language files from somewhere, upload them to the right directory, and finally change it through the language switcher.
WPLANG constant is semi-deprecated and doesn’t work like before. It is used as a fallback when English (United States) or empty language option is selected. For example, if an initial installation is English but your wp-config.php has WPLANG with non English locale, WPLANG’s language files are automatically installed during the installation process.

See: https://core.trac.wordpress.org/ticket/15677

Releasing local packages as usual might be a good idea since it contains local language files in the first place. That always guarantees users to have a choice to switch back to his/her local language without complicated manual steps.

Mattias Tengblad 6:01 am on August 29, 2014

Good points! I agree.

As is, at least packaged language files should be offered for easy download on 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/ sites.
- Dominik Schilling (ocean90) 11:35 am on August 29, 2014
  
  Localized packages will still be available, they are not gone.
  - pavelevap 12:16 pm on August 29, 2014
    
    Whole localized packages will be available (bundled with WordPress)? And what is the difference between localized package and English package with new installation screen? I do not understand it… Also nacin wrote, that 3.9.2 was last time for building packages by translators?
    - Dominik Schilling (ocean90) 1:46 pm on August 29, 2014
      
      The difference is, that a localized package includes the translation files and the global `$wp_local_package` variable is set. That highlights the translation in second place in the language chooser on install.
      
      AFAIK the packages will be generated automatically.
      - Mattias Tengblad 2:09 pm on August 29, 2014
        
        Sounds fair. Is this properly tested?
        
        Yet I still agree with Marko in the comment below.
      - pavelevap 6:53 pm on August 29, 2014
        
        OK, thank you! I thought that there will be only one English package and everything will be set (and downloaded) during installation. And there will be also only small language package with localizationLocalization Localization (sometimes shortened to "l10n") is the process of adapting a product or service to a particular language, culture, and desired local "look-and-feel." files for automatic updates (automatic language packs). And, in WP 4.0 translators will not create language packages when they think it is done, but it will be made automatically even if it is not ready (or waiting until all is translated)? I like the current situation when nobody knows how it will really work some days before release 🙂
      - pavelevap 7:51 am on August 30, 2014
        
        I thought about it once more and still does not understand it fully. When there will be same localizationLocalization Localization (sometimes shortened to "l10n") is the process of adapting a product or service to a particular language, culture, and desired local "look-and-feel." installation packages (like in 3.9.x), only generated by script – so what is the point of installation screen which is featured as 4.0 new function? When Czech user downloads Czech installation package, then he usually (99,9 %) wants Czech version. Now he will have to go through the new installation screen (language chooser) and that is one more (in most cases not needed) step to do, so it looks like regression 🙂 So there should be only one English version for installation package to justify new installation screen?
Marko Heijnen 9:50 am on August 29, 2014
- I hate the first part and I will check the ticket out this weekend to see what the possibilities are.
- Unsure about your second point. WPLANG is now a fallback when the option doesn’t exist in the database. I need to check the code what happens when the option value is empty (switched back to English). I never experience setting WPLANG constant would trigger automatically downloading files.
I’m planning to integrate showing the language package state on http://wpcentral.io/internationalization/ and hopefully soon that list will be included somewhere here.
- Knut Sparhell 5:43 pm on August 29, 2014
  
  > I never experience setting WPLANG constant would trigger automatically downloading files.
  
  It does. It has for many years.
  
  1. Install a localized 3.9.2 version with 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/ A
  2. Change WPLANG to locale B in wp-config.php
  3. Go to update-core.php and it will say a new version is available
  4. Click Update
  5. Observe the new language B in action and the B language files in wp-content/languages
  - Marko Heijnen 8:54 pm on August 29, 2014
    
    That is pretty cool. Will play with that tomorrow 🙂

Translate WordPress

Weekly Meetings

Posting here

Share this: