View Single Post
Old 06-20-2020, 04:14 PM   #84
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: 79,142
Karma: 144284184
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 j.p.s View Post
You keep focusing on writing with intent to control rendering rather than writing to express, when rendering is supposed to be up to renderers and users of renderers.

In a color enabled terminal, the text output HTML renderer lynx uses a different color to render text enclosed in <em></em>.
This is not a good idea to have <em> be a different color with eInk.

It doesn't matter what the intent is if the output doesn't show differently. How many people are going to look at the code to see if you used <i> or <em> for the italics? Plus, I've seen a number of eBooks that used <em> for italics.

I've seen no examples of <em> doing something different other then be italic. And Lynx is not an eBook renderer.
JSWolf is offline   Reply With Quote