Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

In contenthandler, allow specifying an encoding for file content #121

Open
svanoort opened this issue Dec 10, 2015 · 1 comment
Open

In contenthandler, allow specifying an encoding for file content #121

svanoort opened this issue Dec 10, 2015 · 1 comment
Labels
enhancement help wanted
Milestone
1.8.0 Parsing+Sco...

Comments

@svanoort
Copy link
Owner

Without an encoding it will be read as raw binary data (example for images, etc). (This is for safety).

By supplying an encoding we allow it to be converted to (unicode) text for use in templating even when the file body contains non-Unicode data.

Ties to the Unicode epic: #104
@svanoort svanoort added this to the 1.7.0 - Python 3 + Parsing/Configuration Internals milestone Dec 10, 2015
@svanoort svanoort mentioned this issue Dec 10, 2015
Closed
@svanoort svanoort modified the milestones: 1.8.0 Feature additions after first refactorings, 1.7.0 - Python 3 + Parsing/Configuration Internals Dec 12, 2015
@svanoort
Copy link
Owner Author

Postponed to 1.8.x release because it really isn't critical to be honest -- no user demand so far.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement help wanted
Projects
None yet
Milestone
1.8.0 Parsing+Scoping Enhancements
Development

No branches or pull requests
1 participant
@svanoort