We're not supporting this level of localization at the moment. You'd need a message key for each row in the database that's localized. The CR design is to tag each CR entry with a language - this dates back to the original aD design of the CR. This makes sense for complex content, i.e. just provide multiple translations for each item as a separate object and tag by language. Since the CR is often used to store word and pdf data and the like translations by message key doesn't really make much sense in this context, IMO.
Object pretty names can be internationalized and we do it for package names and the like, where we store something like "#forums.pretty_name#" as the package pretty_name then translate it before displaying it (on HEAD this is now done automatically).
