Q: on string translations

[Bruce Frederiksen]

OK, we're going to have strings in the code and strings in the templates that need to be translated.  For this, the standard gettext solution is fine.

But we'll also have strings in the database the need to be translated; e.g., questions, answers, and the names of diagnoses.

The question is does it make sense to use gettext for these too?  Or should the translations also be stored in the database?

Arguments for gettext:

• everybody understands it
• there are translation services that use this (don't know any details here, do these services accept other homegrown formats?)

Arguments against gettext:

• these strings change too often to nail them down in a static file
• do we want the translations versioned too?

Thoughts?  Ideas?  Solutions?

-Bruce

FWIW: If we decide gettext is the answer, Pyramid has a pyramid.i18n.TranslationString class for this.