Add l10n support

[fabricedesre]

Correct me if I'm wrong, but I see no l10n infrastructure in this code.

[nickdesaulniers]

Excellent point! @fabricedesre , would you recommend webl10n?

[fabricedesre]

For now yes. There's an ongoing effort to move gaia to l20n but it's not ready yet and will be quite similar in terms of APIs.

[nickdesaulniers]

I think @basta had mentioned that webl10n did not have support for attributes, IIRC. So things like placeholders wouldn't get localized. But, I really don't remember.

[fabricedesre]

I would be surprised. You can check with @fabi1cazenave to be sure.

[fabi1cazenave]

webL10n supports attributes, and it’s rather simple:

<input type="text" data-l10n-id="userName" />

and in your *.en-US.properties file, just add:

userName.placeholder = User name…

[nickdesaulniers]

Oh perfect, thanks @fabi1cazenave !

[nickdesaulniers]

Need to add placeholders

[nickdesaulniers]

@fabi1cazenave , I'm seeing a CSP warning in the app validator. Does webl10n violate CSP for privileged apps?

[nickdesaulniers]

@fabi1cazenave , should I be using webL10n from gaia instead?

[fabi1cazenave]

@nickdesaulniers the main difference between Gaia’s l10n.js library and the one in webL10n is that the latter is cross-browser — hence a slightly different API and a few fallbacks for IE<9. In other words:

• you can switch to Gaia’s l10n.js library if you’re OK to change the API;
• you can keep webL10n and just remove the whole “if (!window.JSON) {…}” block if you don’t care about IE6 or IE7;
• you can keep webL10n and remove the whole “else if (window.attachEvent) {…}” block if you don’t care about IE<9.

Hope this helps!

[nickdesaulniers]

@fabi1cazenave , great info, I added it to webl10n's wiki.

[fabi1cazenave]

Great, thanks!