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/. 67 locales up to date. 0 locales behind by minor versions. 10 locales behind by one major version. 15 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. 66 locales at 100%. 1 locale has more than 95%. 3 locales have more than 90%. 22 locales have more than 50%. 61 locales have less than 50%. 9 locales don’t have a WP project.
We have a new locale that’s being worked on: nl_BE
The Belgium General Translation Editor A General Translation Editor (often referred to as GTE) is a person, who has global access to validate strings on all projects for a specific locale. Dave Loodts (@daveloodts) tries to get the translation ready for WordPress 4.6.
No (visible) changes so far.
Translation management UI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. experiment
Sam Sidler talked about a new approach to improve the design for GlotPress GlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org., which will be worked out by Issac Keyet (@isaackeyet). More information can be found in a separate blog post at https://blog.glotpress.org/2016/06/08/exploring-design-for-glotpress/
For a brainstorming, all polyglots are asked, to sketch their ideas for a translation interface, no matter whether you are a designer or not. The result should be a collection of ideas, not an exact list of features.
Feedback is expected in the comments under the above mentioned post. Sketches, thoughts and random comments are useful and we should all give it a think and say what’s important to us. The more people join the better. 🙂
Cross Locale PTEs–feedback on Nao’s final proposal
Next step in the process is to define the role and decide on the criteria for becoming a cross-locale PTE A Project Translation Editor (often referred to as PTE) is a person, who has access to validate strings on a specific project (for example BuddyPress, WooCommerce or Twenty Fourteen) for one specific locale. A project translation editor can approve strings that are added by translation contributors. Per project translation, editors are appointed by a general translation editor after a request by the project author or by the contributors themselves.
Draft by Naoko Takano (@nao) for the definition:
A Cross-Locale Project Translation Editor A Cross-Locale Project Translation Editor is an account owned by a plugin or theme author (or the authoring organization), which uses professional translators to localize their product. The cross-locale project translation editor can import/validate strings on a specific project for more than one locale. This role has the same capabilities as a Project Translation Editor over multiple locales instead of one. Cross-Locale Project Translation Editors need to meet a set of criteria before being appointed by General Translation Editors. is an account owned by a 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 or theme author (or the authoring organization), which has can validate strings A string is a translatable part of the software. A translation consists of a multitude of localized strings. on a specific project for more than one locale. This role has the same capabilities as a Project Translation Editor A Project Translation Editor (often referred to as PTE) is a person, who has access to validate strings on a specific project (for example BuddyPress, WooCommerce or Twenty Fourteen) for one specific locale. A project translation editor can approve strings that are added by translation contributors. Per project translation, editors are appointed by a general translation editor after a request by the project author or by the contributors themselves. over multiple locales instead of one. Cross-Locale Project 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 need to meet a set of criteria before being appointed by General Translation Editors.
The current draft of the criteria is:
- Use the community style guides and glossaries, or create ones based on them and provide public links.
- Disclose the sources of translation (e.g. translation vendor) and reviewers (.org username)
- List steps for other .org community volunteers to get involved in the review process
- Create a new account for this role rather than using a personal one, and fill in the profile page with contact information
- Have a Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. account and ping The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” GTEs (TBD – unless auto-notification is possible) after imports
Besides some practical issues (What if their reviewers do not have a wordpress.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? Does that mean they’re no good as translators/reviewers?) it was discussed, how the import of translations by cross-language PTE should be handled.
As we discussed multiple times people with access get tempted to accept pending translations they can’t evaluate. Importing means they’ve been given a file from their translators. Approving means they’re submitting something to production that was community suggested and hasn’t been reviewed.
The Spanish polyglots team Polyglots Team is a group of multilingual translators who work on translating plugins, themes, documentation, and front-facing marketing copy. https://make.wordpress.org/polyglots/teams/. discussed, they don’t like to let anyone approve translations without supervision. Their team suggested bulk imports and set the terms to “Waiting approval”, which in technical terms currently isn’t possible. @petya pointed out, that we spoke about that matter before and the point of cross locale PTEs was to allow these accounts to import without supervision beforehand.
Raffaella Isidori (@zetaraffix) said, the Italian polyglots would like to know how it is assured that the workload doesn’t fall back on the community, hindering rather than improving the flux. Raffaella also asked, how many plugins initially will be involved.
Naoko Takano (@nao) thinks, the involvement of cross-locale PTEs won’t become a complicated hierarchical organization, as they get the same permissions as a regular PTE–just across multiple locales. For now, Automattic plans third party translations for Jetpack, WooCommerce, and VaultPress. As Akismet is included in the core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. package, it may need a different treatment.
The question came up, whether we should add a rule that Cross locale PTEs should only import and not approve at the same time. Obviously that can’t be enforced if we’re going to use the same user role. Yet it is questioned, how approving pending translations can be safe if the person approving doesn’t speak the language.
Christian Herrmann (@presskopp) would like to see an organisation chart to get a better overview over the entire process.
General sentiment is, to give the experiment “cross-locale PTEs” a try.
If cross-locale PTE’s fail to to follow community guidelines, they’ll not continue to be able to import.
FAQ page of the handbook & videos
Pascal (@casiepa) reports, that the FAQ has been published, special thanks go to Naoko (@nao) for a review.
The FAQ can now be found at https://make.wordpress.org/polyglots/handbook/frequently-asked-questions/
The first 7 questions have been published and more are in progress.
The Global Translation Day Videos have been published and are available at https://wordpress.tv/event/global-wordpress-translation-day-2016/ It would be great if a volunteer could go over the meta data of the videos and quickly check that the correct video was linked with the correct meta data.
Farhad Sakhaei (@parsmizban) reported his view of the current situation in the Persian Polyglots team and that many translation strings could need some improvement. Farhad complains, his proposals have been entirely rejected by their translation editors. There seem to be some open questions regarding organizational matters, which need to be clarified in the near future.