MobileRead Forums - View Single Post - How's this for one heck of a messy chapter header?

DNSB · 06-12-2024, 12:50 AM

Personally, I would open the book in Sigil and run my collection of saved searches and plugins—the majority of my saved searches are Vellum specific and yes, I would end up with something like:

Code:

<body>
  <div role="doc-chapter" epub:type="chapter">
         <h2 class="chapnum">DANNER</h1>

         <p class="trifecta">FEBRUARY 1943</p>

        <p class="center2">Dachau, Germany</p>
...
...
  </div>
<body>

Please note I left the first div with the role: and epub:type as I prefer to see them. And this is before I run AccessAide on the epub.

If Jon whinged about InDesign, Scrivener, Jutoh, etc. as often as he whinges about Vellum, it might be more palatable. Instead, he endlessly grumbles about Vellum. I used a quick Google search "jswolf vellum site:mobileread.com" and it comes up with a <expletive deleted> larger number of hits than a similar search for InDesign.

I have to agree that a Vellum produced ebook is not clean and simple code. OTOH, I believe that those of us who look at the code are a very small minority and the overwhelming majority will simply enjoy reading the book. On the gripping hand, Vellum has remained very consistent over several versions making the cleanup task very automatable so a task that once took me 10-15 minutes now takes about 2-3 minutes.

06-12-2024, 12:50 AM	#10
DNSB Bibliophagist Posts: 46,648 Karma: 169712392 Join Date: Jul 2010 Location: Vancouver Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos	Personally, I would open the book in Sigil and run my collection of saved searches and plugins—the majority of my saved searches are Vellum specific and yes, I would end up with something like: Code: <body> <div role="doc-chapter" epub:type="chapter"> <h2 class="chapnum">DANNER</h1> <p class="trifecta">FEBRUARY 1943</p> <p class="center2">Dachau, Germany</p> ... ... </div> <body> Please note I left the first div with the role: and epub:type as I prefer to see them. And this is before I run AccessAide on the epub. If Jon whinged about InDesign, Scrivener, Jutoh, etc. as often as he whinges about Vellum, it might be more palatable. Instead, he endlessly grumbles about Vellum. I used a quick Google search "jswolf vellum site:mobileread.com" and it comes up with a <expletive deleted> larger number of hits than a similar search for InDesign. I have to agree that a Vellum produced ebook is not clean and simple code. OTOH, I believe that those of us who look at the code are a very small minority and the overwhelming majority will simply enjoy reading the book. On the gripping hand, Vellum has remained very consistent over several versions making the cleanup task very automatable so a task that once took me 10-15 minutes now takes about 2-3 minutes.