Hi MKJ2,
for the general plugin translation we use the translate.wordpress.org system, like most plugins. This comes with the disadvantage that only languages are provided that have translations which are at least 95% complete (including the complete backend!). Since we only need small translations (mostly the button text and label) for the frontend this is not very suitable. Therefore all service specific translations are directly handled in the service specific files in the /services folder. If you need to change the button text or label for a specific service, you can simply open the service file e.g. /services/shariff-twitter.php and change there what you need to change. Since all translations are service specific that seems to be the easiest way. If we would manage files by language instead of by service we would need to change ALL language files every time we add or modify a service.
What I did think about is adding a custom language option in the backend for these special use cases, but haven’t had the time yet to implement it. Maybe in the next version.
Cheers,
JP
Thread Starter
mkj2
(@mkj2)
Hi JP,
thank you. Unfortunately, changing the service specific files is not update-safe, right? You know how customers are: they hit the update button and call you: “Hey, something is wrong with my site. Please fix it!” 🙂
Thanks, Mike
Hi Mike,
yes, all plugin files get replaced by an update including language files. I’ll have the custom language option on my to-do list. That will be update proof and let you easily change it in the options. Are you using multiple languages on your sides or just one?
Cheers,
JP
Thread Starter
mkj2
(@mkj2)
Hi JP,
actually, this is not a multi-language site. My customer wants the button labels to be changed. It would be great to have an option for an update-safe customization.
Thanks again, Mike