-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
UTF-8-BOM not supported #1133
Comments
Thanks for reporting. At the moment we are working to get marked up to date since it has been dormant for a while, so it might be a while before we can address this. @joshbruce what milestone should this go under? |
@UziTech and @shinpou: I agree with your assessment re taking a while. Might have overstretched myself a bit, to be honest. I'm still in assessment mode at the moment. As it stands, this is something of a side project for me to help increase my knowledge and understanding...I see various potentials and will do what I can to ensure all of them as future possibilities moving forward. As I have said, I've never made it this far and it was a pretty high-jump for me...I mean, I'm still figuring out how GitHub organizations work. Appreciate the patience. |
Closing as part of future as this support is not specific compared to a specification. |
Marked version:
0.3.17
Markdown flavor:
Ran marked with default settings:
marked README.md -o test.html
What pain point are you perceiving?
UTF-8-BOM encoding will break markdown on first line but works otherwise normally - if the file begins with a title for example, this will not parse.
Unsure if this counts as a defect, just letting you know, maybe add a note to documentation?
The text was updated successfully, but these errors were encountered: