View Single Post
Old 09-12-2024, 04:18 PM   #17
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: 46,424
Karma: 169098492
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by foosion View Post
The one book I've edited with a Vellum CSS was the most ridiculously complex CSS I've ever seen. How anyone thought that was a sensible way to proceed is beyond me. They could have gotten the same appearance with a much simpler CSS.
For the most part, Vellum is not aimed at those of us who would dig into the internals of the ePub.

Vellum's market is mostly indie authors who write their document in Word or other program generating .docx output and then feed the .docx file into Vellum to generate various flavours of ePub output (ePub2/ePub3, Apple, Kindle, Kobo, Nook, Google, generic) with an option for mobi for local testing on Kindle ereaders/apps. For non-ebook uses, you can generate an print ready output file.

As a group, the authors that I have dealt with are more concerned with generating output that will work without requiring them to know about stylesheets, ebook structure, etc. They do care about not generating masses of complaints.
DNSB is offline   Reply With Quote