Meteor - i18n

meteor

https://atmospherejs.com/tap/i18n
https://github.com/TAPevents/tap-i18n/
https://atmospherejs.com/universe/i18n
https://github.com/vazco/meteor-universe-i18n/
https://guide.meteor.com/ui-ux.html
https://themeteorchef.com/snippets/i18n-and-meteor/
http://theosp.github.io/presentations/developing-tap-i18n/#/
http://www.telescopeapp.org/blog/telescope-v0910-i18nscope/
https://atmospherejs.com/tap/i18n
https://github.com/TAPevents/tap-i18n
http://www.meteorpedia.com/read/i18n
https://www.youtube.com/watch?v=cu_dsoIc_0E

Tap
Universe

How can we implement i18n for the accounts system?

i18n is achieved using accounts-t9n. The only thing you have to do is ensure:

T9n.setLanguage('<lang>');

is called somewhere, whenever you want to switch language.

I NEED TO LOOK ELSEWHERE ON THIS WIKI AND UPDATE THIS PAGE.

What are the places that we need to look at when we implement i18n?

  1. HTML templates and components. This is the most obvious placeā€”in the content of UI components that the user sees.
  2. Client JavaScript messages. Alerts or other messages that are generated on the client side are shown to the user, and should also be translated.
  3. Server JavaScript messages and emails. Messages or errors generated by the server can often be user visible. An obvious place is emails and any other server generated messages, such as mobile push notifications, but more subtle places are return values and error messages on method calls. Errors should be sent over the wire in a generic form and translated on the client.
  4. Data in the database. A final place where you may want to translate is actual user-generated data in your database. For example, if you are running a wiki, you might want to have a mechanism for the wiki pages to be translated to different languages. How you go about this will likely be unique to your application.
Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License