WordPress.org

Plugin Reviews

xili-dictionary

xili-dictionary is a multilingual dictionary storable in CPT and terms to create and translate .po files or .mo files and more (import, export...)

4 reviews
Average Rating
3.3 out of 5 stars
Severe language issues in documentation
By , for WP 4.2.2

I wish I could say that I managed ot get my head around this plugin as I really would need a tool that facilitates several language versions of a single wordpress site. Alas, I haven't.

The biggest issue is the documentation of this plugin. I guess the devs try their best to get new users going, but the poor use of English language makes it very difficult to understand what they want you to do. This weighs in particularly heavy as the interface is rather uninutitive and confusing. The 'Getting Started' page of the plugin's Wiki is a prime example of all of that.

A simple step-by-step guide could wokr wonders. At the very least, provide an explanation what mo and po files are before you let users loose on them.

After several hours of trial and error I have given up.

part of plugins to support a true multi language WordPress
By , for WP 3.9.1

xili-dictionary is a powerful online alternative to the desktop program poEdit and offers a seamless integration into WordPress, themes and plugins that offer multilingual capabilities. I do not know any other multi language plugin (series) that impressed me more than the xili-language plugins. Sometimes it is a bit unclear on how to use or setup a multilingual WordPress with the set of the xili-language plugins but once you learned how to use it is a convenient and reliable way to get WordPress translated and content presented in multiple languages. The best thing is, you do not need to tingle with posts or sites marking parts of the content as being a translation. With the xili-series you have single robust pages that can be optimized for SEO in their own language. You can make use of any kind of options that WordPress offers to each language.

Not straight forward + suffers from poor English
By , for WP 3.9

It seems this might be a capable plugin, I just haven’t been able to wrap my head around it yet.

Just like xili language it suffers from
• …a UI that is not as self-explanatory as I would like it to be, and
• …poor English that makes it hard to understand what to do sometimes

An example of the former is that there is no obvious starting point. You can go into a number of sections of the plugin ("Msg list", "New msgid", "Writer", "Origin") and have no idea what to do with it (at least I did ;-) ).

Even when you go into "Tools, Files po mo" where, as far as I understand, the starting point would be if you want to translate the interface (at least if it hasn’t been translated before, which is the case with my theme Sugar and Spice), there is no real hint about what to do. Guessing eventually led me to the very "Tools, Files po mo" settings page and an option to import a .po file, which in reality was a .pot file (and it was chosen from a list of languages(!) where at the end of the list this file was also appended, it was a strange mix). A few hints along the way would have been useful.

Once the file was imported and I had started translating the texts, I figured I should probably press the "Update sv_SE.mo" button (I’m translating to Swedish, ymmv), but the following text at first deterred me from doing so, which relates to the "poor English" second point above:

Before to use this button, it is very important that you verify that your term list is quite achieved inside the dictionary. It is because the original .mo delivered with theme is updated (erased) !!!

It took a while before I realized that most probably nothing important will be erased since there was no such file for the theme before (but I’m still not 100% sure since I haven’t actually tried it, maybe it updates the sv_SE.mo file in some other default place, not from where I imported the .pot file?).

Further I guess that "verify that your term list is quite achieved inside the dictionary." means that the translation must be complete, since no translations from the original .mo file will be kept, but this also took some twisting the sentence back and forth to figure out.

It would be great if this plugin received some love regarding instructions/UI and language.

Not straight forward + suffers from poor English
By , for WP 3.9

I think this is a capable plugin, I just haven’t been able to wrap my head around it yet.

Just like xili language it suffers from
• …a UI that is not as self-explanatory as I would like it to be, and
• …poor English that makes it hard to understand what to do sometimes

An example of the former is that there is no obvious starting point. You can go into a number of sections of the plugin ("Msg list", "New msgid", "Writer", "Origin") and have no idea what to do with it (at least I did ;-) ).

Even when you go into "Tools, Files po mo" where, as far as I understand, the starting point would be if you want to translate the interface (at least if it hasn’t been translated before, which is the case with my theme Sugar and Spice), there is no real hint about what to do. Guessing eventually led me to the very "Tools, Files po mo" settings page and an option to import a .po file, which in reality was a .pot file (and it was chosen from a list of languages(!) where at the end of the list this file was also appended, it was a strange mix). A few hints along the way would have been useful.

Once the file was imported and I had started translating the texts, I figured I should probably press the "Update sv_SE.mo" button (I’m translating to Swedish, ymmv), but the following text at first deterred me from doing so, which relates to the "poor English" second point above:

Before to use this button, it is very important that you verify that your term list is quite achieved inside the dictionary. It is because the original .mo delivered with theme is updated (erased) !!!

It took a while before I realized that most probably nothing important will be erased since there was no such file for the theme before (but I’m still not 100% sure since I haven’t actually tried it, maybe it updates the sv_SE.mo file in some other default place, not from where I imported the .pot file?).

Further I guess that "verify that your term list is quite achieved inside the dictionary." means that the translation must be complete, since no translations from the original .mo file will be kept, but this also took some twisting the sentence back and forth to figure out.

It would be great if this plugin received some love regarding instructions/UI and language.

You must log in to submit a review. You can also log in or register using the form near the top of this page.