WordPress Translation Plugin – Now Google Translation from and into Turkish, Hungarian, Hebrew, Serbian, Slovak, Slovenian, Catalan, Galician, Indonesian,…

The latest improvements and language pairs added to the Google Translation Engine have been included in the simple WordPress Translation Plugin downloadable from this personal blog.

It now includes links to automatic translations from and into all language pairs offered by Google Translation Engine, apart from other language pairs (from individual languages, like English) into other online machine translators, viz Tranexp.

Available language pairs now include (new pairs in bold): English, Albanian, Arabic, Bulgarian, Catalan, Chinese (Simplified and Traditional), Croatian, Czech, Danish, Dutch, Estonian, Filipino, Finnish, French, Galician, German, Greek, Hebrew, Hindi, Hungarian, Icelandic*, Indonesian, Italian, Japanese, Korean, Latvian, Lithuanian, Maltese, Norwegian, Persian*, Polish, Portuguese, Romanian, Russian, Serbian, Slovak, Slovenian, Spanish, Swedish, Thai, Turkish, Ukrainian, Vietnamese, Welsh*.

*These languages are only offered as languages to be translated into from the English version.

New Version for Spanish Translation Plugin and Translator Widget Released

I don’t have a lot of time to post content on this blog, but at least there are some other WordPress-based websites I have to care of, and they usually include some type of a modified WordPress Translation Plugin.

The Spanish-Catalan translator link didn’t work right, and because of that I substituted it for another translation engine; a Spanish-Galician translator engine has also been added to the plugin, both from the Translendium engine. These two modifications are released with the new Spanish Translator Plugins dnghu_es_h and dnghu_es_v.

Because I have more than 5 (and more than 10) WordPress sites, and because I am used to work with widgets, I’ve finally developed the plugin into an easy-to-install Indo-European Translator Widget, which is actually more of the same code. If you are more used to widgets, or if you don’t need/want to place the translation links outside the sidebar, or if you just like the plug-and-play advantages of widgets, this might be your best option.

(I’ve tried to create a plugin account at WordPress.org for the widget, because now it’s not only about 10 lines of code, and new releases might be for security risks or other bugs – however, three weeks after requesting it, I haven’t received permission yet; I guess I’ll wait a little more and then publish it on the web – I just don’t want to upload things twice, or work more than necessary ūüôā

It might seem paradoxial,¬†as¬†I’ve¬†changed the plugin for the widget on this site, whilst in the widget’s site I’ll probably use the plugin: it’s a question of advantage balancing – and, in this very case, of the WordPress themes I’m using for each site.

Indeed, it remains the simplest possible code a non-professional like me could write, so¬†you’ll¬†probably be¬† able¬†to¬†modify¬†and¬†customise it if and when¬†you¬†want ūüėČ