Explain standards and approach to translation, and language files.
A rapid sweep through all of the existing modules is required to enable the static strings (mostly flash messages) to use the req.t function.
Although i18n is nice, realistically, most sites will not need it. Whatever approach is taken should take a least-overhead approach so that most sites will not be encumbered with needless function calls.
Agree, though I think the Drupal model of just wrapping static strings in t() functions is neat and simple (better than the java way of coming up with msg labels for everything), and if you don't care then you don't use it - its just that your site (or module) can then never be translated.
@cliftonc, grepping through the code-base, it looks like all text passed to flash() is using req.t()
No, I think largely that most things should be wrapped now, I just need to get some documentation written that explains it, and improve the process for creating a base language file for translation ...
I noticed this today: mashpie/i18n-node, will re-write translation library to use this.