View Single Post
Old 04-28-2020, 06:52 AM   #16
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 80,044
Karma: 147977995
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by TheTechAuthor View Post
That was an interesting read. Thank you.

However, my main concern is getting a workflow that "just works" across KDP, Google Play Books, and iTunesConnect. Right now, from a speed perspective at least, <em> for emphasising words and <b> for bolding words is the quickest - for me.

I need to work within the currently accepted rules of whatever digital eBook store I want to sell on. And, as it currently stands, as valid as <I> is, it's not accepted in ePub 3 by every eBook retailer. Sadly.
<em> is no faster then <i>. There's no difference between them. If your text is already using <i>, just let it be. There's nothing wrong with <i>.
JSWolf is offline   Reply With Quote