Not straight forward suffers from poor English

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.