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!
4 Replies
@jvinga, you just advanced to level 2!
@Gali Baum
One reason being, when you're in the template, on the UI, there is no (apparent) ways to define which one you're using.@jvinga what do you mean by that? In the ui you would use
translationGroupName.translationKey for example {{i18n sign-up.welcome}}
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?Could you give an example? I'm not sure I follow 😬
Oh I was not passing the translationGroupName, it makes sense I'll try it with the group names. Thanks!