Thread: Extended <head> chapter: NOT necessary?
View Single Post
Old 03-06-2017, 11:23 AM   #65
Turtle91
A Hairy Wizard
Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.
 
Turtle91's Avatar
 
Posts: 3,369
Karma: 20212733
Join Date: Dec 2012
Location: Charleston, SC today
Device: iPhone 15/11/X/6/iPad 1,2,Air & Air Pro/Surface Pro/Kindle PW & Fire
Quote:
Originally Posted by JSWolf View Post
With an eInk Reader, how would the following words in <em> look?

<i>This is a test of the <em>emergency broadcast system</em>.</i>

I tried this using Calibre's viewer and all I got was a line of italic text. <em> showed nothing. So without using CSS to redefine <em>, what do you get? If you have to redefine <em>, why not use <span> with a class?
ummm... I got this one:

1) you're not "redefining" <em> you are "styling" how you want the word emphasized with CSS...which is what you are supposed to do. The default style for <em> is italicized, that does not make it the ONLY way to emphasize some text.

2) <i> is specifically a font style (font-style:italic) - it changes the display but it semantically does nothing

3) <em> is shorter than <span class="yadayada"> and designed specifically for emphasizing words. So it is semantically more correct.

4) I'm willing to change my outlook (and coding) based on new standards rather than continually argue about how it used to be done. I'm willing to look at different ways of doing things instead of insist everyone use my way...

5) I do not code for e-ink devices exclusively. I code for how I want the product to look with today's technology and standards. If a publisher cares about backwards compatibility then they can add the appropriate CSS to handle the different media types...which is much easier to do if you have the proper semantic markup. It is silly to intentionally limit all of your reader's experiences to e-ink capabilities. E-ink readers are not the only devices out there...as a matter of fact their use has dropped considerably. "One of the main problems is that e-reader devices have failed to develop in any major technical form since their introduction in 2008." (stats found in the article "The E-Reader Device is Dying a Rapid Death") note: The article is referencing e-ink devices when they say "e-reader" - another section talks about ebook sales skyrocketing and attributing that to the prevalence of smart phones and tablets.

Cheers,
Turtle91 is offline   Reply With Quote