We could also go down a very different route and try to configure auth0 not to send emails and just send them ourselves and configure i18n well inside our app (which we're going to have to handle somehow anyway for #767 ).
Or perhaps create some scripts that will play well with the rest of the i18n flow and will generate the 3 email templates we need and then it'll just be a matter of copy/pasting them into Auth0 every time there is an update to the Auth0 messages? And use this as an opportunity to make all our emails look less like they're a tacky postcard sent in the 90s and stuck all these years somewhere in some mail processing facility and only found and delivered now.
Unfortunately Auth0 does not provide translated versions of their Universal Flow emails.
The best descriptions for how to internationalise those emails that I've found are here:
And here's a feature request for making this i18n process saner (with 7 votes at the moment, including mine, so not likely to happen any time soon):
We could also go down a very different route and try to configure auth0 not to send emails and just send them ourselves and configure i18n well inside our app (which we're going to have to handle somehow anyway for #767 ).
Or perhaps create some scripts that will play well with the rest of the i18n flow and will generate the 3 email templates we need and then it'll just be a matter of copy/pasting them into Auth0 every time there is an update to the Auth0 messages? And use this as an opportunity to make all our emails look less like they're a tacky postcard sent in the 90s and stuck all these years somewhere in some mail processing facility and only found and delivered now.