Open
Conversation
Building the `Last-Translator` string fails if the User class doesn't have `first_name`, `last_name` or `email`. We pass building the data if a UnicodeDecodeError occurs. I think we can skip building these data when a custom User class is being used as well (for now).
Use classes only to assign Javascript functionality to the “See translatable items”, “See non translated items” and “Apply changes” buttons.
merge django 1.6 fix
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I don't recall the exact problem. But using scandics (åäö) would break at times with smart_str