Locale 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/ stats
Releases: 162 locales 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/. 62 locales up to date. 0 locales behind by minor versions. 12 locales behind by one major version. 20 locales behind more than one major version. 60 locales have a site but never released. 8 locales don’t have a site.
Translations: 162 locales. 59 locales at 100%. 7 locales have more than 95%. 6 locales have more than 90%. 27 locales have more than 50%. 54 locales have less than 50%. 9 locales don’t have a WP project.
Releasing the well-translated locales that are behind more than one major version
A week after release of WordPress 4.6 we are happy about the great number of releases. There are several locales that are behind more than two major versions, even though they have been almost entirely translated. We have 6 locales that can release, even though they’re not at 100%. A couple of General Translation Editors Translation editors can approve translations for projects. The GTE (General Translation Editor) and LM (Locale Manager) roles can add new users with the "Project Translation Editor" role that can approve translations for specific projects. There are two different Translation Editor roles:
General Translation Editor and Project Translation Editor already have been asked to get in contact with Petya (@petya) (see Behind one or two major versions – releasing 95%+ locales for WordPress 4.6).
A look at Waiting strings A string is a translatable part of the software. A translation consists of a multitude of localized strings. for Plugins and Themes
https://translate.wordpress.org/stats lists the number of waiting text strings for all locales. The statistics show, that we have a growing backlog of waiting text strings. Some locales currently handle the validation by asking translators to ping them in their local community Slack, after a translation has been finished. This is problematic as users might make mistakes constantly that could have been corrected after the first 10 text strings they submit. This approach also doesn’t reflect the priority that plugins and themes should have due to their popularity. (Pascal (@casiepa) has generated a page that lists the top 120 plugins at http://wp-info.org/plugin-top120/)
It was also discussed, that it is currently difficult for plugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party/theme developers to bring their translators into the GlotPress GlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org. translation process. Wolly (@wolly) suggests to insert into the handbook a link to the script that Yoast uses to call translators (https://github.com/Yoast/i18n-module).
Documentation sprint update
No more comments are allowed on any page of the handbook (https://make.wordpress.org/polyglots/handbook/). If you find any mistakes, please report on the Polyglots channel in Slack.
Handbooks on local w.org
Pascal (@casiepa) opened a ticket to get the handbooks (like https://make.wordpress.org/polyglots/handbook/) on the local xx.wordpress.org sites to be able to give more structured info. It’s a great and easy way. It will take some time, but eventually we might get it (only 1 per locale!) https://meta.trac.wordpress.org/ticket/1919
Open discussion
Pascal (@casiepa) gathered some links to statistics on his personal website: http://wp-info.org/polyglots-stats/ Petya (@petya) will ask Dominik (@ocean90) to include this information on the official Polyglots pages.
#weekly-meeting-notes, #weekly-meetings
