daybed i18n for validation errors

i18n for validation errors

Open leplatrem opened this issue 13 years ago • 3 comments

trafficstars

Apr 22 '12 17:04 leplatrem

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?

Apr 22 '12 20:04 almet

Yep, should be okay :)

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

Apr 23 '12 12:04 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"]]

Jun 01 '12 14:06 leplatrem