Thanks for the review!
You have a good point with the scanning method, however if the interface were to use a “pick a theme/plugin” method, there’d be an issue with it listing all plugins and themes which might not have any translation files in them (not sure if that’s much of an issue). Also, I wanted to make sure all files under wp-content/languages could be accessible (such as the WordPress core translation files, and ones that are somehow used but not aren’t easily associated to a plugin/theme). However, I could probably just offer a field that lets you input the full file path to the file you want to edit, for advanced users. Again you have a point with the plugins/themes-first method and I’ll look into that in the near future.
The only plans for additional features are things like creating a POT file, creating PO files from a POT file, and a restore feature for backed up original of a file that’s been edited. I’m also toying with adding a source-code viewer that will allow you to view where in the code a translation is to appear, but I want to make sure it’s done right.
thanks for the comment and consideration for the plugin/theme/system first route.
The thing is, when using plugins like this you do it with a goal in mind. I already know what theme/plugin/system I’m going to translate, because that’s why I installed the plugin. This really is a very minor pet peeve. I’m really glad a solid option to do translations from within the WordPress admin exists.
I would not mind if no translation files were found after a scan. Especially if you follow up with the new feature of creating them.
Why I said that I hope it doesn’t add too many bells and whistles is because I like plugins that do one thing good and isn’t intimidating for new users. Sorry to say, but I think a full path field is never going to be used by anybody, it’s all about discoverability.
Remember, I’m just one user with, what seems, a very strong opinion on these things. Don’t read to much in to this, I really like the plugin.
Also, what do you mean by this?
…, and ones that are somehow used but not aren’t easily associated to a plugin/theme
Is that when plugins or themes are _doing_it_wrong?
Is that when plugins or themes are _doing_it_wrong?
I’m honestly not sure, I just want to make sure that any PO file can be edited by the user, and don’t want to screw them over just because the plugin/theme they’re trying to edit isn’t setup properly.
See, I didn’t even think of that 🙂
That’s a very good point to scan for all the files. Thanks for answering my questions and making this plugin.
