View Single Post
Old 01-09-2026, 05:37 PM   #34
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 51,399
Karma: 179640714
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by JSWolf View Post
Vellum also needs to go away forever because it creates the some of the worst code ever. Sure it's valid, but if you need to make changes to the ePub, it's may not be easy especially if the person doing the changes is not knowledgeable enough in HTML/CSS.
Valid code that works. That you seem to think that an automated code generator should create code that matches your preferred coding style says more about you and less about the generated code. Unless you can post an example where Vellum produces code as an example, that makes the page display slow down, there is nothing wrong with it.

And really, do you think someone who is using Vellum is also going to be manually editing the ePub? For the authors I know, that is generally where I have the offending ePub sent in my direction for fixup instead of the author wasting valuable writing time on learning CSS/XHTML.
DNSB is online now   Reply With Quote