After lots of debug and digging inside local middleware I have fixed this. To solve this I had to add LOCALE_PATH in settings file.
On Friday, July 22, 2016 at 6:41:44 PM UTC+5:30, Sonu Kumar wrote:
-- On Friday, July 22, 2016 at 6:41:44 PM UTC+5:30, Sonu Kumar wrote:
Hi there,I would like to add a custom language to support for i18n. You can check my question here http://stackoverflow.com/questions/38511925/add-custom- . I have followed all the steps mentioned here http://stackoverflow.com/language-for-localization-in- django-app questions/19267886/adding-a- .custom-language-to-django In short, the steps are as follows1. add a custom language(NEW) dictionary to settings file and update LANG_INFO dictionary2. add new language to LANGUAGES as well for i18n to detect3. compile message for the new languageProblem is that when I visit the home page with new language code then it redirects to /en/NEWCan somebody point out the error or make it working?
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/62765b9d-8e24-4758-ae11-e8f73b330940%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment