i18n for validation errors

[leplatrem]

• find a way to specify expected language

[almet]

I think this can be a part of the HTTP specification, because there
already is a "accept-language" header that we could use for this.

Isn't it enough?

[leplatrem]

Yep, should be okay :)

I posted this issue as a reminder, so that we don't get stuck eventually

[leplatrem]

Colander seems to manage i18n already, it should be plugged with accept-language then.

What about translations of fields ? descriptions ? choices ? Should they be pushed along with model definition ?

"description": "age?", "description:en-US": "age bro'?", "description:fr": "âge?",

It means we have to define choices as tuples :

"choices": [["big","Big"], ["small", "Small"]], "choices:fr": [["big","Grand"], ["small", "Petit"]]