I am the 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. author for Lang Forge and I would like to request 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. so I can maintain its translations properly.
- https://wordpress.org/plugins/langforge/
— pl_PL – @avakodeforge
I want to be upfront about where these translations come from, because I know this page says machine translation without human review by a speaker of the target language is not an acceptable source.
We are a very small team and cannot hire translators for 15 languages. The catalogues were machine-generated. When the plugin was approved, the directory imported the bundled languages/ folder into the project automatically — that is where the current Russian, Dutch, Czech and Swedish percentages came from, not from any contributor.
Before posting I built the closest thing to review that I could. I downloaded WordPress core Core is the set of software required to run WordPress. The Core Development Team builds WordPress.’s own translations for each of these 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/ and compared every string A string is a translatable part of the software. A translation consists of a multitude of localized strings. of ours whose English source is byte-identical to a core string — 201 strings A string is a translatable part of the software. A translation consists of a multitude of localized strings. per 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/. 975 diverged from core. Each divergence was reviewed individually and 692 were corrected, keeping 283 where core’s string comes from an unrelated context. Divergence from core is now 299. That shipped in version 1.0.28.
It found real errors, not just style preferences: two Hindi strings still in English and one that said the opposite of what it meant (“Disconnect”), an Italian false friend (“Editore” for Editor), French missing its non-breaking-space typography and WordPress’s inclusive role forms, Russian using “посты” where core has said “записи” for twenty years.
I understand that this is a process and not a native speaker, and that for 14 of these locales it does not meet the bar this page sets. I am asking anyway, because the alternative is imported strings sitting in your projects with nobody able to correct them.
ru_RU is the one I can genuinely vouch for — I am a native speaker.
For any locale where your team would rather not grant this, please just say so and I will remove the imported strings for that locale so they are not left there unreviewed. I would rather ship nothing than something wrong. I am also happy to publish the full per-string review with its reasoning if that would help you judge.
If you have any questions, just comment here. Thank you!
#editor-requests
