Added BOM support #26
Merged
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
Now skipping the BOM if it exists
artonge
reviewed
Oct 23, 2023
|
Hi, of course ;) Here is the official unicode docs on BOM: https://www.unicode.org/versions/Unicode15.1.0/ch02.pdf#G27981 For UTF-8, the BOM only signals that the document is using unicode: https://www.unicode.org/faq/utf_bom.html#utf8-2 An issue on this topic indicates, that the reader should skip over it: golang/go#33887 |
|
I am unsure whether this logic really belongs here, but why not :) |
artonge
approved these changes
Oct 24, 2023
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.
Now skipping the Byte Order Mark (BOM) if it exists. Old version would include the BOM in the first header field, so it would not match the specified fields correctly.