It is currently only the frontend part of the website that support translations. This means that the website's user will always recieve the requested email from the backend in english, no matter the language the website has been translated to. It would improve the overall user experience, if the email sent shared the same language. This can be accomplished by completing the following tasks:
[ ] Add the language code of the enabled language as a parameter in the api-call to the backend.
[ ] Implement i18n support natively in the backend.
[ ] Write simple translations to the content of the email.
[ ] Handle the given language code parameter in the HTTP-request within the component_controller by changing to the requested language if available.
[ ] Load the content of the email from the proper translation files.
Thank you for helping out the development of this project by placing your first issue. The team behind nwa will address its issues as soon as possible. Best regards, the developers.' first issue
It is currently only the frontend part of the website that support translations. This means that the website's user will always recieve the requested email from the backend in english, no matter the language the website has been translated to. It would improve the overall user experience, if the email sent shared the same language. This can be accomplished by completing the following tasks: