Developer take care of the…

Developer take care of the translators!

Yes, I am a developer and translator and I see a bad behaviour that it is easy to fix and can help the translation of your pluginPlugin 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 Plugin Directory or can be cost-based plugin from a third-party from the community.

First rule: No automatic translation! As I already said on the last WP Translation Day the English language is not very good for translation and it is easy to spot when they are automatic. The communities have a glossary and rules that the automatic translator doesn’t follow. So the PTEProject 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. has to check every stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings. that usually is rejected and that time could be used to approve beautiful translations.

Second Rule: Why put your name as developer and links of your website or of the plugin site under the __(),_e() etc? GlotPressGlotPress GlotPress is the translation management software that powers More information is available at detect them and ask to translator to translate! It’s useless!

Do you have any other rules for the developers that need to be followed to improve the life of a translator?