@diox Are you talking about coming from ES? Yes, that sucks. I had planned to store these as a nested document in ES something like `{'lang': ..., 'text': ..., ...}` and on serialization pick the right one. For fields that we don't need to search we can just stash them in ES that way. For fields we do need to search we need to explode them out at the top level like we do with names and descriptions (e.g. `name_es, name_fr` and assign it the right analyzer.

But you're right, we really should close this hole.