-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Ignore byte order mark in the head of UTF-8 text. #1149
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
Conversation
7dde688
to
1d28aa5
Compare
Add a testcase about bom.
The CI failed in Visual Studio environment, this error is weird, does anyone have a clue about this?
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved, but please add the length-check if you have time. If that doesn't fix the VS crash, then we'll have to investigate further I guess. We can't merge until AppVeyor passes.
This is approved, so you're free to merge it. My general rule is that if a PR is logically a single commit, we can simply "squash" rather than creating a new merge-commit. You can see that option in the drop-down next to "rebase and merge" if you're not familiar with it. Sometimes, I prefer to retain several commits for the history, in which case I create a new merge-commit. I think I'll change the default to squash, since "rebase and merge" is rarely what we want (since it does a "fast-forward"). |
(That uses This is a mess. For the new branch, I really think you're better off using |
Fix issue #1141