View Single Post
Old 02-22-2017, 09:41 AM   #59
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,228
Karma: 148951761
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 GrannyGrump View Post
@jswolfe --- not a real-world example in the sense you mean, but I have created experimental projects where I set the <em> to be Large Red font, instead of *italic, and <strong> to Large BLUE font instead of *bold*.

As chaot and BetterRed noted about semantics earlier in the thread, I have started using <i> and <b> for things such as foreign language, book titles, and such. Then I want the <em> and <strong> when showing, for example, someone shouting their dialog. This is really more for ease of editing the code, rather than concern about TTS, although that does enter into it a bit (can't hurt, might help).
But you do know that you can swap how <i> & <em> work via CSS. So technically there is no difference. <b> & <strong> also are not different.
JSWolf is offline   Reply With Quote