inlyne VS rust-cssparser

The closest thing currently is probably https://github.com/trimental/inlyne which differs in two ways: it only support markdown not arbitrary HTML, and it renders to screen rather to an image. But it's a good start.

IMO the main blocker for web rendering in Rust right now is better text layout, and in particular support for embedding non-text content within text ala `display: inline-block`. If/when that is implemented I think we'll be able to do a decent job of rendering basic web pages.

Specifically the conversion happens here

Using a cargo-xtask task to generate them as a manual step (inlyne currently does this)

Checkout github.com/trimental/inlyne if you're interested in this project or try it yourself with cargo install inlyne. Happy to answer any questions.

If you wanna know more check the [GitHub homepage](https://github.com/trimental/inlyne) or play with cargo install inlyne

If you were to implement this yourself, i'd look into either swash or cosmic-text for the text rendering stack (this is one of the things you really don't want to write from the ground up). For accessibility, AccessKit has quickly become the standard for communicating with crossplatform accessibility APIs in rust GUI. lightningcss (or its lower level counterpart cssparser) are both decent options for CSS parsing. Taffy handles some of what browsers offer for a layout engine, but is still being worked on.

Libraries for a lot of this stuff exist (albeit in many cases not very mature yet):

- https://github.com/pop-os/cosmic-text does text layout (which Taffy explicitly considers out of scope)

- https://github.com/AccessKit/accesskit does accessibility

- https://github.com/servo/rust-cssparser does value-agnostic CSS parsing (it will parse the general syntax but leaves value parsing up to the user, meaning you can easily add support for whatever properties you what). Libraries like https://github.com/parcel-bundler/lightningcss implement parsing for the standard css properties.

- There are crates like https://github.com/BurntSushi/bstr and https://docs.rs/wtf8/latest/wtf8/ for working with non-unicode text

We are planning to add a C API to Taffy, but tbh I feel like C is not very good for this kind of modularised approach. You really want to be able to expose complex APIs with enforced type safety and this isn't possible with C.