Documentation about i18n approach #23

Open
cliftonc opened this Issue May 21, 2011 · 6 comments

Projects

None yet

3 participants

@cliftonc
Owner

Explain standards and approach to translation, and language files.

@cliftonc
Owner

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.

@dennishall
Collaborator

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.

@cliftonc
Owner

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.

@jzacsh

@cliftonc, grepping through the code-base, it looks like all text passed to flash() is using req.t()

  • Is there anywhere else I should look?
@cliftonc
Owner

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 ...

@cliftonc
Owner

I noticed this today: mashpie/i18n-node, will re-write translation library to use this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment