View Single Post
Old 03-24-2016, 02:34 PM   #55
dgatwood
Curmudgeon
dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.
 
dgatwood's Avatar
 
Posts: 629
Karma: 1623086
Join Date: Jan 2012
Device: iPad, iPhone, Nook Simple Touch
Quote:
Originally Posted by JSWolf View Post
It won't work because it's the same character and Kindles treat em-dashes the same no matter how you code it. There is no secret coding you can use to get a Kindle to to treat an em-dash any differently.
That is true only on pre-KF8 Kindles. The newer Kindle devices use WebKit for rendering, which does respect zero-width nonbreaking spaces.

BTW, I just edited my previous post. I don't know why I thought I was using zero-width joiners (which shouldn't work). I was actually using zwnbsp, which is different, and any properly functioning (Unicode-compliant) HTML/XHTML renderer should treat it as an indication that the line should not be broken at that point even if it otherwise would be.

Last edited by dgatwood; 03-24-2016 at 02:36 PM.
dgatwood is offline   Reply With Quote