I18n and translation files
I was wondering what would you suggest as per translations variables, having multiples files or one big that you update?
One reason being, when you're in the template, on the UI, there is no (apparent) ways to define which one you're using.
we were about to use somehow same keys in different translation files so maybe the right approach would be to have like a big i18n files with different objects for each email?
Looking for how you guys want us to use those translations!
Thanks!
One reason being, when you're in the template, on the UI, there is no (apparent) ways to define which one you're using.
we were about to use somehow same keys in different translation files so maybe the right approach would be to have like a big i18n files with different objects for each email?
Looking for how you guys want us to use those translations!
Thanks!
