Improve email localization

[fnagel]

• User email localization should be based upon subscription post language
• Remove admin email localization: otherwise admin email localization depends on FE action or default (when sent from BE)
• Use translation string for user emails

[fnagel]

It seems its currently not possible to use Fluid translation features within backend. There is no way to force a specific localization. Neither for Tx_Extbase_Utility_Localization::translate nor for the related VH. Tried to hack a workaround without success. Help wanted.

Using a setting option for configuring a template per language uid would be an alternative. This wold not help with translating the email subject and, of course, is a very non TYPO3 conform way of fixing this.

Conclusion
Translation of emails is currently not possible. Adding localization strings help only when email is generated in the FE aka is approved and non spam from the beginning.

[fnagel]

See here: https://wiki.typo3.org/How_to_use_the_Fluid_Standalone_view_to_render_template_based_emails

[fnagel]

Take a look at: http://typo3.org/extensions/repository/view/reint_mailtask_example

[fnagel]

http://www.derhansen.de/2015/10/fluid-standaloneview-translation-scheduler-task.html

[pixelbreit]

Hi, is there in the meantime a way to use different email templates (subscription opt-in, new comment notify for user) based on used frontend language?
Maybe a conditon to select alternative email templates or template folder?
Using t3extblog 2.2.1 with TYPO3 7.6.11

[fnagel]

Not sure, but I don't think TS conditions will work. Only if you make sure no emails are sent from within the BE, but than it should work with localization VH anyway.

You could try to work with multiple sys folders. Never tried before.

I guess this feature would need some more testing and some adjustments in code for a easy and correct language handling.