u/EidolonTypeset

Drop Caps and custom formatting shattering on older Kindles (CSS Fallback Trap)

I spend a lot of time deep in my digital workings, manually stripping out bloated converter code and rebuilding semantic EPUB architecture for authors most of the time. I wanted to drop a warning about a formatting regularity for reader experience on e-ink devices

A lot of authors use Vellum or Calibre to force fancy Drop Caps or custom chapter headers. The previewer looks great. But when you upload it to KDP, readers may immediately complain that the first letter is floating above the paragraph, or the line-spacing is overlapping

This happens because automated converters often use absolute pixel values (px) or points (pt) to force layouts. When a reader opens your book on a Paperwhite and changes their default font size or switches to a dyslexic font, the absolute CSS refuses to scale. Thus it shatters

The fix is entirely in the CSS writing. You have to strip the absolute values and code your typography using relative em or rem units, and use clean <span> tags for drop caps. This forces the architecture to mathematically scale alongside whatever rare font settings readers may have

If you rely on automated converters, test your file on an actual device and radically alter font styles if necessary. If it breaks, your CSS may be too rigid

reddit.com
u/EidolonTypeset — 5 days ago

Drop Caps and custom formatting shattering on older Kindles (CSS Fallback Trap)

I spend a lot of time deep in my digital workings, manually stripping out bloated converter code and rebuilding semantic EPUB architecture for authors most of the time. I wanted to drop a warning about a formatting regularity that wrecks reader experiences on e-ink devices

A lot of authors use Vellum or Calibre to force fancy Drop Caps or custom chapter headers. The previewer looks great. But when you upload it to KDP, readers may immediately complain that the first letter is floating above the paragraph, or the line-spacing is overlapping

This happens because automated converters often use absolute pixel values (px) or points (pt) to force layouts. When a reader opens your book on a Paperwhite and changes their default font size or switches to a dyslexic font, the absolute CSS refuses to scale. Thus it shatters

The fix is entirely in the CSS writing. You have to strip the absolute values and code your typography using relative em or rem units, and use clean <span> tags for drop caps. This forces the architecture to mathematically scale alongside whatever weird font settings readers may have

If you rely on automated converters, test your file on an actual device and radically alter the font styles. If it breaks, your CSS is too rigid

reddit.com
u/EidolonTypeset — 6 days ago

Drop Caps and custom formatting shattering on older Kindles (CSS Fallback Trap)

I spend a lot of time deep in my digital workings, manually stripping out bloated converter code and rebuilding semantic EPUB architecture for authors most of the time. I wanted to drop a warning about a formatting regularity that wrecks reader experiences on e-ink devices

A lot of authors use Vellum or Calibre to force fancy Drop Caps or custom chapter headers. The previewer looks great. But when you upload it to KDP, readers may immediately complain that the first letter is floating above the paragraph, or the line-spacing is overlapping

This happens because automated converters often use absolute pixel values (px) or points (pt) to force layouts. When a reader opens your book on a Paperwhite and changes their default font size or switches to a dyslexic font, the absolute CSS refuses to scale. Thus it shatters

The fix is entirely in the CSS writing. You have to strip the absolute values and code your typography using relative em or rem units, and use clean <span> tags for drop caps. This forces the architecture to mathematically scale alongside whatever weird font settings readers may have

If you rely on automated converters, test your file on an actual device and radically alter the font styles. If it breaks, your CSS is too rigid

I am a backend EPUB architect. If you get tired of fighting the code and want your manuscript hand-coded cleanly from scratch to pass strict W3C validation, I'm right here ;)

reddit.com
u/EidolonTypeset — 6 days ago

[For Hire] I offer brutally analytical Beta Reading for Sci-Fi, LitRPG, and Progression Fantasy

Most beta readers sugarcoat their feedback for the sake of sparing your feelings

I do not

I am an analytical sci-fi/fantasy writer and systems architecture dev. I read heavy mechanics-based web serials, Dumas, and Dostoevsky. I am looking for plot holes, pacing drag, weak magic economies, and broken character logic

What you get from me:

  • Blunt inline notes exactly where the narrative drags and I wanted to skip
  • A mechanical breakdown of logical inconsistencies in character decisions
  • Stress-testing your world-building logic (economy, physics, magic limits)

I do not do fluff or toxic positivity. I act as the debugger for your manuscript. If your protagonist's survival logic makes no sense, I will point it out

Send a DM with your genre, word count, and a brief synopsis

reddit.com
u/EidolonTypeset — 6 days ago

[For Hire] I build cleanEPUBs for Indie Authors and offer LatAm Spanish Localization (W3C Validated)

Most authors use Calibre or Vellum, which inject bloated "ghost code" into the backend, causing Amazon KDP to format strangely on older devices or fail validation

I am a technical EPUB dev. I do not use automated converters--I strip the manuscript down to its core and rebuild it using semantic HTML5 and CSS. Every file I deliver passes strict W3C EpubCheck 3.3 validation, ensuring flawless cross-device rendering

Services Provided:

  • Standard English EPUB Typesetting: $15+
  • The LatAm Localization Stack: I translate your Sci-Fi/Fantasy/LitRPG novel into natural Latin American Spanish, build the valid EPUB, and prepare it for Amazon MX and ES

Portfolio & Code Validation Proof: markbox.cc/eidolon-typesetting

Send a DM with your word count and what you need done--all work is handled securely via Fiverr Escrow

reddit.com
u/EidolonTypeset — 6 days ago

Most authors use Calibre or Vellum, which inject bloated "ghost code" into the backend, causing Amazon KDP to format strangely on older devices or fail validation

I am a technical EPUB dev. I do not use automated converters--I strip the manuscript down to its core and rebuild it using semantic HTML5 and CSS. Every file I deliver passes strict W3C EpubCheck 3.3 validation, ensuring flawless cross-device rendering

Services Provided:

  • Standard English EPUB Typesetting: $15+
  • The LatAm Localization Stack: I translate your Sci-Fi/Fantasy/LitRPG novel into natural Latin American Spanish, build the valid EPUB, and prepare it for Amazon MX and ES

Portfolio & Code Validation Proof: markbox.cc/eidolon-typesetting

Send a DM with your word count and what you need done--all work is handled securely via Fiverr Escrow

reddit.com
u/EidolonTypeset — 23 days ago

Most beta readers sugarcoat their feedback because they want to spare your feelings

I do not

I am a highly analytical sci-fi/fantasy writer and systems architecture developer. I read heavy mechanics-based web serials, Dumas, and Dostoevsky. I am looking for plot holes, pacing drag, weak magic economies, and broken character logic

What you get from me:

  • Blunt inline notes exactly where the narrative drags and I wanted to skip
  • A mechanical breakdown of logical inconsistencies in character decisions
  • Stress-testing your world-building logic (economy, physics, magic limits)

I do not do fluff or toxic positivity. I act as the debugger for your manuscript. If your protagonist's survival logic makes no sense, I will point it out

Send a DM with your genre, word count, and a brief synopsis

reddit.com
u/EidolonTypeset — 23 days ago