Hello Marcos.

Translator plugins like WPML are able to translate the static strings, but dynamic strings like Notification templates, service names, personal names, any custom fields you enter, and so on cannot be translated.

That's a limitation of translator plugins, and unfortunately there's nothing we can do about it. The dynamic strings are strings which can be added or changed by anyone, so the translator plugins' logic cannot work around that.

My advice would be to reach out to WPML's team, and ask them if there's a way the plugin could translate dynamic strings, although I never heard someone was able to do that.

Hello İbrahim.

Thank you for contacting us. The same answer I provided for Marcos applies here:

Translator plugins like WPML are able to translate the static strings, but dynamic strings like Notification templates, service names, personal names, any custom fields you enter, and so on cannot be translated.

That's a limitation of translator plugins, and unfortunately there's nothing we can do about it. The dynamic strings are strings which can be added or changed by anyone, so the translator plugins' logic cannot work around that.

All static strings are translatable by WPML, Weglot, PolyLang, etc. You can add gibberish to be a dynamic string, or abbreviations - that's why they can't be translated. If you make a typo in a dynamic string, it will not be translated. For instance, in my native language (Serbian) - there's no word for "sibling", so it can't be translated at all. If you enter a service name, or expect translator plugins to translate notification templates, it's not going to happen. Maybe the question should be forwarded to WPML, and see if they are working on translating dynamic strings.