id,summary,reporter,owner,description,type,status,component,version,severity,resolution,keywords,cc,stage,has_patch,needs_docs,needs_tests,needs_better_patch,easy,ui_ux 31132,Django Internationalization Issue,Tiago Borges,nobody,"I have a application in django 2.2 to translate just as below: {{{ LANGUAGES = ( ('pt', _('Portuguese')), ('en', _('English')), ('es', _('Spanish')), ) LANGUAGE_CODE = 'en' USE_I18N = True }}} The translation itself is working on the templates and for the default language (LANGUAGE_CODE). The issue lies on the translation triggering. Since this is for a REST api, I will not be using cookies or sessions, the translation needs to watch the `Accept-Language` header. Debugging the Locale middleware, I can confirm that the correct language is being found, but the translated text are returned always for the default language (LANGUAGE_CODE), ignoring the language found by the middleware. If I replace the `LANGUAGE_CODE` for pt or es, it works just fine. The django docs states that `LANGUAGE_CODE` was supposed to be the last fallback. ",Bug,closed,Internationalization,2.2,Normal,needsinfo,internationalization,,Unreviewed,0,0,0,0,0,0