Package translations not working with Meteor 1.3 (beta 8)

[nicooprat]

Couldn't make it work with latest version of Meteor 1.3. Tried a lot of configurations based on the docs and code from live apps like Telescope, but all strings was displayed with their keys and not their values. No problem with project-level translations though.

Anyone got it to work ? Is it a known issue ?

[SachaG]

I think it's a known issue. For Nova I've temporarily removed i18n.

[Andrew1431]

Any progress on this...

[luckyyang]

Any progress on this？

[Andrew1431]

@luckyyang we moved our translations from each package in to a seperate translations package that loads before all other packages. This solution got all the translations working properly.

[nicooprat]

I stopped using packages at all and followed more or less the Mantra spec https://github.com/kadirahq/mantra

[derwaldgeist]

Any solution for this?

[deehuey]

Yeah, with latest Meteor you can use npm modules, so I would suggest just switching to the normal npm tapi18n package, and using imports.

[derwaldgeist]

Hm. How exactly does that solve my problem that i18n does not work in Meteor packages? I don't want to switch the app's packages to npm packages, because I want to keep it in a modular fashion. Reason is that I am sharing a lot of the Meteor packages across apps.