plutobook

https://github.com/plutoprint/plutobook was a recent Show HN and looks excellent

Thanks for your questions! 1. The documentation for HTML and CSS parsers is pretty straightforward and easier to implement, so I thought it was better to write them myself. 2. It fully supports margin boxes (headers and footers) using properties like @top-left and @bottom-center inside @page rules. You can see more here: https://github.com/plutoprint/plutobook/blob/main/FEATURES.m... 3. Yes, I did come across this. Fragmentation logic is as difficult as it sounds. Right now PlutoBook works with a single, consistent page size throughout a document and does not support named pages, which simplifies things a lot. Feel free to contact me via email if you have more questions.

PlutoPrint supports a large subset of CSS, including flexbox for most common layouts, but it’s not a full browser engine, so there are some limitations. You can see a more complete list of supported features here: https://github.com/plutoprint/plutobook/blob/main/FEATURES.m.... We’re also actively tracking bugs and improvements on the GitHub repo: https://github.com/plutoprint/plutoprint/issues, and contributions or test cases are always appreciated to help expand coverage.

CSS coverage is stated in [1]. It should be required to do minimal assessment before entitledly posting on HN. [1]: https://github.com/plutoprint/plutobook/blob/main/FEATURES.m...