#142 i18n strings in database

[Kevin Campbell]

At present, we cannot deal with this effectively.

One immediate solution which was tried in 2.1 was to
i18n the strings before sticking them into the
database. Annoyingly PTS requires both a request object
(PTS stores a cache in there) and an instantiated zodb
object for context. This isn't possible in init or
manage_afterAdd, as each only has one or the other.

The general solution would be to extend some text
fields in the database to a tuple of (textfield,
msgid). If msgid is set, the translated string from the
i18n set would be used. This code would be common in a
number of places.

Leaving as an RFE for now. In 2.1 all default text will
be generated in English.