markdown-clipper VS tidy-html5

I am on a Mac and I use firefox. The extension I use for capturing part or the entire webpage in markdown is https://github.com/deathau/markdown-clipper

If you're using it as a template language for your own pages, you can of course just write it correctly (this is not different than needing to use correct syntax for react code to compile).

If you have someone else's documents, or need to mass convert your own to fix them, there's HTML tidy[0]. This one is quite useful to be able to run XML processing CLI tools on scraped web pages.

But the real power is in delivering XML to the client, not HTML. This lets you work in domain model directly on the frontend, and use XSLT to transform that into HTML for display. So of course you'd use well-formed XML in that case.

[0] https://github.com/htacg/tidy-html5

So I included the tidy libraries in my project.

Maybe look into HTML Tidy. It's job is to clean up HTML and convert legacy code to modern form, so it knows about DTDs. You might be able to pass it some options to get what you want.

I've always used tidy for HTML/XML formatting jobs.

Personally I use command that switches the file type to html, and then formats it with tidy. It assumes you're pasting into a new buffer.

I use tidy.

So I installed HTML tidy.

Prune instructs the parser to remove any elements within the extracted article block that look superfluous. This can result in false positives, so we tend to disable it when we've gone to the trouble of creating site-specific extraction rules.

Tidy determines if the source HTML should be cleaned up first with HTML Tidy - https://github.com/htacg/tidy-html5. If you're parsing the source HTML with an HTML 5 parser, as we are now, it shouldn't be necessary any more (I think we actually ignore it now). We used it more before when we relied on libxml parsing, which often trips up on modern HTML.