[WIP] use Accept-Language header in jinja templates #3942
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
solves translation issue where jinja used server-side LANG environment and javascript used browser configuration via the Accept-Language header, which could result in multiple languages on the page. Now, all browser messages should be consistent with the browser settings.
Introduces caching of gettext translation objects to ensure that we don't keep loading the translation config on every request.
cc @JCEmmons
TODO: