That is so important. as a growing company which needs to translate email in 10 different languages and maybe 20 tomorrow, it is hard to manage 10 times the normal amount of template.

Hello.

I just posted an EXACT same request not knowing this one existed, 'cause the search engine for this feedback forums kinda sucks.

https://feedback.mailjet.com/forums/931474-feature-requests/suggestions/47318996-basic-locale-support-for-templates-i18n

I'm 100% with you on this.

I manage mail templates in multiple languages.
So far i have to create and maintain one of each using suffixes.

foo FR
foo EN
foo CN

bar FR
bar EN
bar CN

...
please.

And although there is support for variables, variables are supposed to be small concise piece of data. Complete email translation won't do it.

Could we imagine a "locale" support - it would allow to creates variants of a template for different locales, be organized under a common "folder".

foo
- FR
- EN
- CN

bar
- EN
- FR
- CN

Or the other way around where the user could filter by a desired locale and see a list of all template for that locale only.

Hypothetical advance feature could be :
- detecting a missing locale support for a template (let's say i forgot FR for reset password idk..)
- generating a quick translation from an existing template from some translation bot

Thus, Send API could accommodate a new parameter "locale", maybe.

the premises of very basic i18n support in a nutshell.. :)

Best.

It would be very awesome to be able to create internationalisate-able email templates. Means: I create a template within a default language and would then be able to translate it for other languages by adjusting texts, use different images and so on. Via the send api i should then be possible to pass a language next to the template ID. If the template exists in this language: use it, if not: use the default one.

This would really help my in my internationalization and would be an awesome feature for Mailjet!

It's a massive pain to handle email translations right now. There's also very limited documentation on the whole thing as well. Ideal solution is as this mentions, to have a single template ID that can have multiple translations. From the backend implementation it's simple, specify template ID + language. Having a template for every language just adds unnecessary complexity.

Hi,
I also stumbled with the same issue. Any updates regarding this request?

Hi there. I also have this issue. Is there a solution yet?

Hi,
Would it be possible to add other languages in the list offered in the transactional templates settings ?