Marcjultrad, January 15, 2017
Implementing translation plugins in WordPress can be quite challenging, depending on your aims and needs. For instance:
- are the free resources offered by a solution enough for you?
- is a manual correction resource important?
- is there a theme, a template you absolutely want to use?
Such factors can make this process a lot more painful than the one of installing, say, a chat plugin.
A good procedure is to address the translation issue right from the beginning, implementing or trying a solution step by step, intercalating the work of producing the texts in the main language with that of translating them, then publishing at least a few pages and testing how things are going, instead of first producing the whole site in one language for then to start thinking about its version into others, what resource you should use and so on.
The main problems do not concern the translation itself, but actually how the plugin displays it, how it works. The ideal would be to make the internationalization decisions in conjunction with the other initial decisions when creating a site.
A very important one to have in mind, especially when using plugins with huge data bases as is the case of internationalization softwares, is that many times when you click to save a setup things won’t always happen instantly. Very often you have to wait some time. Therefore, fast and safe as WordPress may be, patience here is of the essence.
Things may also not happen due to other causes – an icon, a country flag for instance, indicating another language in which the site can be browsed may not be displayed because no content was inserted into any page under that icon yet, although that page has been created, placed under a menu and published.
In the video below you will find a comparison between the WPML plugin and its competitors Multilingual Press, qTranslateX and Polylang (in this last one the free resources include a good translating editing capability):