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. / translation review request for Onsite Link Verdict
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.
- https://wordpress.org/plugins/onsite-link-verdict/
The plugin ships translated into the seven 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/ below as of version 0.7.0 (124 of its 129 strings A string is a translatable part of the software. A translation consists of a multitude of localized strings.; the five left in English are URLs and the brand name). Right now those translations only live inside the plugin package, so they are not in translate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins. and there are no language packs.
— de_DE – @onsitetools
— es_ES – @onsitetools
— fr_FR – @onsitetools
— it_IT – @onsitetools
— nl_NL – @onsitetools
I want to be upfront about how they were made, because I know it matters to you: they were produced by me, the author, with AI assistance, and they have NOT been reviewed by a native speaker of each language. I am fluent in Portuguese and reviewed pt_PT and pt_BR myself; the other five I cannot vouch for personally. They are not raw machine output dumped through a translator – each string A string is a translatable part of the software. A translation consists of a multitude of localized strings. was translated in context, the placeholders were checked programmatically against the originals, and untranslatable items were deliberately left empty rather than guessed – but I am not going to claim a quality I cannot prove.
So I would rather ask for what actually helps, and leave the choice to each team:
1. If your team is willing to review them, I will gladly hand over the .po files PO files are human readable files which contain translations we use. These files are not used by WordPress itself. Each language will have its own PO file, for example, for French there would be a fr_FR.po file, for german there would be a de_DE.po, for British English there might be en_GB.po. and take whatever corrections you send. That is the outcome I would prefer.
2. If your team would rather assign an existing active translator as PTE instead of me, that is completely fine and I will not ask again.
3. PTE for me is only useful so that I can import the files in the first place – I have no interest in approving anyone else’s work in a language I do not speak.
A note on why the wording matters more than usual for this plugin: it is a broken link checker, and most of its strings are plain-language explanations of what a server actually answered (“the server is refusing automated checks, it is not telling us the page is gone”). A stiff translation there does more damage than an untranslated string, which is exactly why I would like human eyes on it.
If you have any questions, just comment here. Thank you for your time – I know you are volunteers.
#editor-requests
