View Single Post
Old 12-20-2012, 07:54 AM   #11
Ripplinger
350 Hoarder
Ripplinger ought to be getting tired of karma fortunes by now.Ripplinger ought to be getting tired of karma fortunes by now.Ripplinger ought to be getting tired of karma fortunes by now.Ripplinger ought to be getting tired of karma fortunes by now.Ripplinger ought to be getting tired of karma fortunes by now.Ripplinger ought to be getting tired of karma fortunes by now.Ripplinger ought to be getting tired of karma fortunes by now.Ripplinger ought to be getting tired of karma fortunes by now.Ripplinger ought to be getting tired of karma fortunes by now.Ripplinger ought to be getting tired of karma fortunes by now.Ripplinger ought to be getting tired of karma fortunes by now.
 
Ripplinger's Avatar
 
Posts: 2,387
Karma: 2368269
Join Date: Dec 2010
Location: Midwest USA
Device: Sony PRS-350: 3 Silver, 2 Blue!; Kobo Glo
The book I'm doing has no spaces before and after the em dashes so I want to keep it that way. But I can't find a way to prevent the orphans that works consistently. If I use & # 8288 ; (without the spaces, or it wouldn't display)⁠ before the em dash in Sigil for instance, Sigil's viewer displays what looks like a thick pipe character. Calibre's viewer shows a space. When loaded on my Sony 350 though, it looks perfect... no space, no odd character, and no orphan em dashes.

Is it safe to assume it will work on all ereaders correctly then as it does on the Sony or might it depend on the font used? Or is there a different code to use in Sigil so that it will display correctly no matter where viewed, cell phones, PC, Sigil, Calibre, etc?

You would think that software across all platforms could follow certain rules to avoid orphans of certain characters.
Ripplinger is offline   Reply With Quote