i18n

Closes #16 

I have two issues with this approach:

 - I sincerely do not like putting all strings into the `i18n.js` file (that's why I built that grunt task to split it into several .properties file);

 - I would much rather have access to the HTML, retrieve the text and then insert the needed strings than using the `{nlsn}` property. But I guess this will have to do, since I can't really access the HTML contained inside the `{@section}` helper.
It's bad practice to fragment i18n strings — fragments are hard to contextualise and are not necessarily translated according to the same rules.  It's fine to keep HTML in the string to be translated, and in some circumstances it may even be helpful to allow localised URLs.