The language file for "./i18n/en-us" could not be automatically loaded. A fallback will be used instead
See original GitHub issueOn a clean install, Django 1.10, I get the following message:
The language file for "./i18n/en-us" could not be automatically loaded. A fallback will be used instead
I see that in the src and dist folders the translation files don´t have the sublanguage suffixes.
What´s the best practice here?
Issue Analytics
- State:
 - Created 7 years ago
 - Comments:30 (19 by maintainers)
 
Top Results From Across the Web
Translations - No fallback used if requesting english variant
Another fix that involves no code changes is to at least have it documented that you should have always a translation (and with...
Read more >Force Django to show English as fallback - Stack Overflow
Just use the English translations as the message IDs. ... you can set the variable LANGUAGES in your settings file, which is described...
Read more >How to fallback to default language when listing nodes in a ...
I have a list of projects, mostly in english, but some are translated in French. When i visit the French version of my...
Read more >django-parler - PyPI
Nice admin integration. Access translated attributes like regular attributes. Automatic fallback to the default language. Separate table for translated fields, ...
Read more >django-modeltranslation Documentation - Read the Docs
The modeltranslation application can be used to translate dynamic content of existing Django models to an arbitrary number of languages ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Just to note when you change the value to
<html lang="en">versus<html lang="en-US">the warning goes away (and gain a slight performance increase in the case of many select2 fields on the page).I would like to resolve the issue since its affecting the load speed of the admin site. The static files seem to wait for this to load and with multiple inlines its really having an impact.