Hello Martin.

The e-mail templates are dynamic strings, and are not affected by translation strings. 

If you wish to change them to a different language, the whole WordPress has to be in that same language. Or simply translate them manually.

Sorry for the inconvenience.

Best regards.

Hello again Martin.

When you're using dynamic translating plugins like PolyLang, WPML or Weglot, you need to have a .po file for the language you wish the plugin to be translated in.

If you were to change the WordPress's language to one that Amelia has a translation for (for example German), everything will automatically be translated. But, the thing is that we don't have the Czech language file, so you would have to create it.

Words can be changed using POEDIT or Loco Translate for example very easily. I suggest you to install Loco Translate and then to translate these string.

If you want to use POEDIT then this is an instruction:

1. Download the Amelia plugin from our TMS Store or from email that you receive when you purchase our plugin and save the .zip file on your computer.

2. Unzip downloaded .zip file.

3. You need to download and install POEDIT. 

4. After that open the program and open the file from the extracted folder on your computer ameliabooking/languages/en_US/wpamelia-en_US.po.

5. Translate all the strings on your language.

6. Save the file as it suggests to you (the language code; for example wpamelia-id_ID.po if your language is Indonesian) and it will be generated new  wpamelia-id_ID.mo file. Find your language code here. 

7. Go to ameliabooking/languages/ folder and make new folder and call him as language code for your language (in our case for Indonesian is id_ID) and  then copy these two files called wpamelia-id_ID.po and wpamelia-id_ID.mo and then copy hole folder id_ID back to your website in the location ../wp-content/plugins/ameliabooking/languages/.

Of course, you will use language code for your language (we use Indonesian language and his language code is  id_ID just as example)

When you finish that it would be nice to send us that translation, so we can include in next major update so you don't have to copy this folder from local machine on every update.

Hope this helps. If you have any more questions, don't hesitate to ask.

Best regards.

Hello again Martin.

That's what I understood in your initial comment.

What I don't understand, though, is if you want to translate the body of the e-mail or the names of notifications on the left. If you're talking about the body of the e-mail, I already replied to that, saying that e-mail templates are dynamic strings, and are not affected by translation strings from the .po file.

So, from your screenshot I see this:

If you translated the .po file into Czech, these strings should all be translated, as they are translated for German:

But, even if the plugin is translated into German, the body of the e-mail still stays in English:

When you retype this in another language, it is stored in the database in a different language, and this being dynamic strings means .po files are not affecting the bodies of e-mails - just like you said:

These are not included in POT file, this is saved directly into the database

Notifications, service names and service categories' names cannot be translated, but only retyped.

Kind regards.

Hi all.

I understand your disappointment, but unfortunately I don't believe our team will be able to do anything with this, and the request would have to be turned to the translator plugin's team.

Dynamic strings are user created and saved in the plugin or theme options, in user meta or in a custom table the translation plugin doesn’t know about. In our case that's the "wp_amelia_notifications" table in the database. This is something that users can change from within the plugin - a dynamic string, similar to the service's name. So - defining a service's name will stay the same no matter what language you translate the plugin to. If you change the name to "Allemagne" for French, it will not automatically be changed to "Deutschland" when you switch to German, or "Germany" when you switch to English. It is something you typed in yourself, and that cannot be changed so easily.

Same goes for Notification templates. They are template e-mails which you can (should) change to be specific to your use case. That is why, for example, if you're using "Language Tool" or "Gramarly" chrome add-ons - they have to be turned off when you're changing the Notification templates, because if you use these spell-checking add-ons they will overwrite the Notifications content in the database itself, and you will wind up with a blank template.

You would need to reach out to WPML, Weglot, PolyLang or whichever translator plugin you're using for multi-language website, and ask them how you can add the dynamic strings into the translation. You now have the database table we're using for the Notifications, so if there is a solution to this, they'll probably help you out.

Kind regards.

Agreed, Martin.

Unfortunately we don't have hooks (action and filters) at the moment. What we have is a few JS hooks that is triggered depends on the view:

window.beforeAddToCalendarLoaded()
window.beforeBookingLoaded()
window.beforeSearchLoaded()
window.beforeSearchFiltered()
window.afterSearchFiltered()
window.beforeConfirmedBooking()
window.beforeCatalogLoaded()
window.afterSelectCatalogCategory(object_category)
window.beforeCatalogCategoryLoaded(object_category)
window.beforeCatalogServiceLoaded(object_category, object_service)
window.afterSearchActivateService(object_appointment, object_serviceActive)
window.afterSearchGoToSecondStep(object_appointment, object_serviceActive)
window.afterBookingSelectDateAndTime(object_appointment, object_serviceId, object_providerId, object_locationId)
window.afterBookingSelectService(object_appointment, object_serviceId, object_providerId, object_locationId)
window.beforeConfirmBookingLoaded(object_appointment, object_service, object_provider, object_location)
window.afterConfirmBooking(object_appointment, object_service, object_provider, object_location)

JS files are modified (minimized) in public version of plugin (in our development environment is accessible), but unfortunately I can not send you our source code because that is the policy of our company.

All those files that have extension .vue are compressed and minimized in JS files that is very hard and not recommended modifying. So in order to add some other features you can unminify the js and customize it.

Best regards.

Hello Dev

Thank you for reaching out to us again.

Unfortunately, at the moment we cannot say that Amelia can be translated easily with any language tool. We're having the same issue you're mentioning with a lot of other languages, including our own (Serbian) - we have 7 grammar cases, and it's extremely difficult to make Amelia be properly translated.

We've recently hired new developers, so we have more manpower. They've started exploring our options with WPML, Polylang, etc and I hope that a decision will be made soon, and we'll move toward this being resolved soon. Thank you for telling us about the add-on for WPML, so each word is translatable. I will forward this info to our developers.

Translation is becoming a pretty big issue with Amelia, so I'll make sure this is highly positioned on our "to-do" list. I can't make any promises as to when the plugin will be ready for WPML or other multi-lingual plugins, but I can promise that we are working on it.

At the moment - it's not compatible, and we can't make it compatible in the near future.