View Single Post
Old 10-05-2024, 08:30 AM   #19
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,043
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 Turtle91 View Post
Jon - I wonder if you read anyone else’s posts…lol
This has been argued multiple times and you’ve been proven incorrect.

- i/b are visual markups
- em/strong are semantic markups
- MOST devices/apps default to italics/bold for em/strong
- accessibility devices/apps can differentiate between semantics and visual markup and thus emphasize a spoken word differently than an italicized (visual only) word
- your css can be adjusted to display emphasize <em>, or strong, words differently than just italics/bold (color, underline, letter spacing, to name a few)

Just because you choose to leave them as default doesn’t mean everyone has to. Please give it a rest.
You can also choose to change how <i> and <b> look using CSS. I have never once seen <i>, <em>, <b>, <strong> changed to anything other then the default.

Last edited by JSWolf; 10-05-2024 at 08:35 AM.
JSWolf is online now   Reply With Quote