jim-a-1020401

The best software for this I’ve seen is Tachyon but it’s way above consumer technology level for cost and compute resources. https://cinnafilm.com/product/tachyon/

Like the interface and OS I assume the TV manufacturers are mostly using cheap versions of what they think they can get away with without pushing up their costs.

I don’t understand why TV manufacturers can’t just have dynamic frame rate change to match the content like Apple ProMotion (https://m.gsmarena.com/understanding_apples_promotion_displa...)

I think it is perceptual but not that specific to the medium. A faster frame rate “feels” closer to reality and the 24fps frame rate is far enough from reality that it’s easier to perceive as “something else” which allows fiction or dramatic content to be perceived differently. I tend to agree with that conception of it. The idea that when the frame rate gets high enough to not be noticeable then the brain treats it more as a real world perception and the standard is higher so it is more harshly judged and ends up seeming as lower quality reality instead of fantasy mode.

No browsers support those features from all the testing I've been doing over the past month or two. Weasyprint supports everything I tried except target-counters and dot leaders which I've only found support for with princexml. Weasyprint does author a proper outline within the PDF so my current workflow (no $ for prince) is to use Weasyprint to make the PDF with a TOC that has no page numbers, extract the outline from the PDF with a python tool to get the page numbers, update the original HTML with page numbers then run it through Weasyprint again. That'll be bundled in an automated build thing triggered by a git commit of the original markdown file straight to PDF so it's not something I have to do manually each time.

That's good for page sizing but as other comments on this thread noted, no browsers seem to have proper support for CSS paged media including Chrome. When I tested it, none of the @bottom type stuff or other print/page related CSS worked at all which is why I ended up with Weasyprint since it has it's own engine (and is really great). Example of some more paged media stuff not supported by Chrome; https://www.smashingmagazine.com/2015/01/designing-for-print.... Another thing Weasyprint does really well which surprised me is automatically carrying over table headers onto subsequent pages when a table is split across pages, which is really nice.

I've been working on a documentation process with Markdown -> HTML + CSS -> PDF for a while and I found that Weasyprint works best. It supports everything I need except CSS target-counter for auto-generation of page numbers in a TOC but otherwise really good.

I really don't like that this uses something non-standard for header/footer and stuff in the margins since that's already covered by standardized CSS @page stuff; https://www.w3.org/TR/css-gcpm-3/. I'm using that with Weasyprint for automatic header/footers with auto page-numbering, including setting strings from the html to use for heading names, document title, author, etc... example CSS: `h1 { string-set: h1-title content(), h2-title ""; }` + `@page { @bottom-left {content: string(h1-title) string(h2-title);}`.

Weasyprint seems closest to princexml and is free.