4 ms·
>Now this is actually the fault of PDF and how it does positioning of stuff within it - but about 50% of the blame lies with whichever software generated a shit
by LordDragonfang 6y ago
>Now this is actually the fault of PDF and how it does positioning of stuff within it - but about 50% of the blame lies with whichever software generated a shit PDF.
Arguably, it's still the fault of the horribly overcomplicated pdf spec -- html manages to do it just fine, with a plain text format, to boot
- kaba0 6y agoWell, it’s an interesting competition, but I believe HTML(+CSS to be fair) would win the complexity of the spec price hands down.
- cycomanic 6y agoShoe me the html document where I can search through a 60 page text. That's actually the thing. Html is fine if you only read text that would be maximal 2 pages on print. But if you read longer documents you want pagination which destroys the ability to search (unless the author implements a separate search or you use Google)
- LordDragonfang 6y ago>Shoe me the html document where I can search through a 60 page text. epub. >An EPUB file is an archive that contains, in effect, a website. It includes HTML files, images, CSS style sheets, and other assets. Search works just fine on ereaders. The flexibility of html is that you can render it however you want, for whatever viewport or feature. If you want pagination, just render it differently. >But if you read longer documents you want pagination For long form works, I do actually prefer having them on my kindle, but that's because I don't want to read long-form text by staring at a screen, and I want a lower line width. PDFs tend to be worst case scenario there, because they often render with the assumption that you're trying to read it on standard letter paper. Also, we've had "pagination" for text files for decades. It's called "less".