From 24aeaded8cfea3e82b923ab4488a989c36b1e2de Mon Sep 17 00:00:00 2001 From: Ernesto Wulff Date: Sat, 24 Mar 2018 16:21:34 +0700 Subject: [PATCH] Fix Spanish internationalization example MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The translation 'Esse campo deve ser unico' is wrong. The right text should look like: 'Ese campo debe ser único'. If you need help translating some parts of the project into Spanish let me know. --- docs/topics/internationalization.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/topics/internationalization.md b/docs/topics/internationalization.md index ed8b85836..517f5d04b 100644 --- a/docs/topics/internationalization.md +++ b/docs/topics/internationalization.md @@ -43,7 +43,7 @@ REST framework includes these built-in translations both for standard exception Note that the translations only apply to the error strings themselves. The format of error messages, and the keys of field names will remain the same. An example `400 Bad Request` response body might look like this: - {"detail": {"username": ["Esse campo deve ser unico."]}} +    {"detail": {"username": ["Este campo debe ser único."]}} If you want to use different string for parts of the response such as `detail` and `non_field_errors` then you can modify this behavior by using a [custom exception handler][custom-exception-handler].