fix issue #161 -- remove utf-8-sig for utf-8 for output files #162
Conversation
This file contains 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
…iles also noticed that the tests don't work with cssutils before ~0.9.10 because the validate kw was not added to parseFile until at least after 0.9.8a3 tests all pass
Closed
1 similar comment
|
Also read this in the Unicode Standard: Use of a BOM is neither required nor recommended for UTF-8 |
|
Thank you very much! |
jorgebastida
pushed a commit
that referenced
this pull request
Mar 2, 2015
fix issue #161 -- remove utf-8-sig for utf-8 for output files
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
also noticed that the tests don't work with cssutils before ~0.9.10 because the
validate kw was not added to parseFile until at least after 0.9.8a3
tests all pass