tidy-html5

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 the 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. Imagine if you didn't have a distinction between APIs and pages; you just returned the data along with a link to a template that says how to display it and (ideally) a link to a schema definition. Modifying templates for compon

I have used Jekyll for over a decade, but for the next iteration of my static personal homepage I am using: POSIX make, POSIX sh, POSIX sed, and tidy. Considering adding POSIX awk to generate a small portion of the HTML from tsv. Also not overly happy about tidy (it is difficult to control its level of output [1]), so I may look for a replacement. [1]: https://github.com/htacg/tidy-html5/issues/996 Why? I have been on a bit of a minimalist streak recently and I wanted to see if I could keep things simple and as close to treating it all as text as possible. So far I have to say that it feels refreshing and trying to come up with simple solutions has made me feel much more motivated to get coding.

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.

Htmltidy is popular as well: https://github.com/htacg/tidy-html5 Though, on second glance, it doesn't do what HtmlWasher is doing here...stripping out classes, etc. It just cleans it up, unmatched tags and so forth.

I recently had an interesting conversation about the use of the HTML 4 transitional doctype, and was surprised to find out that it was no longer valid. I thought this website was the official / final say on the matter, but apparently it is both outdated and "just an informative reference", whatever that means: https://www.w3.org/QA/2002/04/valid-dtd-list.html This is true despite the fact that the best validator I know of, https://validator.w3.org/nu/, agreed this was a valid doctype. But apparently that was a mistake as well, and they recently fixed it so it shows that doctype as an error. So what does it mean for HTML to be versionless? Here is the best I can understand it. The doctype is not supposed to alter the way the browser behaves. Browsers should continue to support outdated elements, attributes, etc for backwards compatibility

Doesn't support tabs, can go DIAF. :-p Or jump in a lake, you downvoting sourpuss sissypants you! Recently went to check, after a >1 decade break. The man page is 5000 words, tons and tons and tons of options. No tabs though. Edit: apparently this feature got added last May! Just waiting on my distro now. Sweet! https://github.com/htacg/tidy-html5/issues/108