Hi @harm10,
All the strings in the plugin can be translated using the normal translation techniques for WordPress. If you’re not familiar with these, I’d recommend you check out the Loco Translate plugin:
https://ww.wp.xz.cn/plugins/loco-translate/
It provides you with a page in your WordPress admin area where you can translate all the plugins and themes on your site.
Thread Starter
Harm10
(@harm10)
Thanks for replying.
Isn’t the normal procedure in plug-ins to use po/mo files for translation?
Hi @harm10,
Yes, Loco Translate generates the .po and .mo files for you. It can also generate the .pot, which I see now is missing from the plugin.
I’ll try to get a .pot file added in an update, but I believe you can also generate one from the Loco Translate plugin.
Thread Starter
Harm10
(@harm10)
Whenever a pot file is missing I try to generate it with POEdit.
This involves picking up text strings that have a specific structure like __('Text', 'text_domain_id')
Does this plug-in use a similar structure and if so what is the prefix?
Hi @harm10,
Yes, it uses the normal technique for translations. It should work with POEdit if you’re familiar with that as well. The textdomain is good-reviews-wp. You can see an example in the code here:
https://github.com/NateWr/good-reviews-wp/blob/master/includes/template-functions.php#L168
Thread Starter
Harm10
(@harm10)
OK. I will investigate and report back.
I didn’t see a translation prefix before the text Read More in the code.
Does this translation work in another way that I am used to?
Thread Starter
Harm10
(@harm10)
Alright I managed to get the string translated.
I created a pot file from the files and then a English po/mo file.
From there I created the desired Dutch po/mo and voilà the string was translated.
Why did I miss this all?
Any way my problem is solved!
Thanks for the support!
Glad to hear you were able to get it working! Thanks for reporting back.
