Notes from the Polyglots chat on May, 11th

Locale stats after the 4.5.2 maintenance release

Releases: 162 locales. 58 locales up to date. 3 locales behind by minor versions. 15 locales behind by one major version. 16 locales behind more than one major version. 61 locales have a site but never released. 9 locales don’t have a site.

Translations: 162 locales. 61 locales at 100%. 3 locales have more than 95%. 5 locales have more than 90%. 22 locales have more than 50%. 61 locales have less than 50%. 10 locales don’t have a WP project.

Next short term goal is getting to 75 locales up to date before 4.6

Technical update

Trac Ticket #r37361-core: In WordPress 4.6 Open Sans is removed and will be replaced with system fonts. Polyglots are asked to test in their locale whether the display of the back end works with system fonts in their native language/characters.

Glossaries in GlotPress

In the #glotpress meeting was discussed if a “Master Glossary” should be tied to a project. Related pull request is
It was widely agreed, that we aren’t a fan of using a (random) project for the master glossary. The team prefers a detached master glossary. More feedback can be left as a comment on the issue or the pull request.

The other technical update is about loading text domains/languages in core for plugins and themes, which will be changed in WordPress 4.6. Previously, if a plugin shipped a translation ​and​ a language pack (from existed, WordPress loaded the one from the plugin. In WordPress 4.6 the translation from will be loaded instead.

Second change is that plugins and themes which have translations on are no longer required to call load_plugin_textdomain() or load_theme_textdomain(). Therefore a number of rules that used to block an import to can be removed.

WordCamp Europe contributor day

We will have an unprecedented number of contributors and many polyglots. It would nice to work out some tasks for Contributor Day and polyglots are asked for ideas either in the comments below or in the next meeting.