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.

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

charset=utf-8 necessary? #8

Open
Nettsentrisk opened this issue Jul 8, 2015 · 1 comment
Open

charset=utf-8 necessary? #8

Nettsentrisk opened this issue Jul 8, 2015 · 1 comment

Comments

@Nettsentrisk
Copy link

For binary base64-encoded data, setting the charset to utf-8 for the data uri doesn't seem to be relevant. You'd only want this if it contained encoded text.

You'll also confuse people using LESS, by thinking they should add the "charset=utf-8" bit as part of the mime type, which turns off base64-encoding using that function, and thus prevents it from being encoded to a data uri.

@jaicab
Copy link
Owner

jaicab commented Oct 23, 2015

Fair enough. I'll have a look at this, thanks!

@jaicab jaicab self-assigned this Oct 23, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants