Thread: &()nbsp , &()#160 , inconsistencies??
View Single Post
Old 08-27-2015, 08:39 PM   #25
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,816
Karma: 6000000
Join Date: Nov 2009
Device: many
What are your Sigil settings for Preserve Entities? And do you have Tidy on open/ save enabled.

If it matters, named entities are not allowed in html5 and so Sigil will be moving to using numeric enties (either hex or not) as defaults for preserving entities.

KevinH


Quote:
Originally Posted by sjkramer View Post
Using Sigil 8.6 on a Mac running OSX 10.10.3. In all the versions of Sigil I've used (at least the last several), I have never had satisfactory handling of nonbreaking spaces. I have had a book rejected from the Google Play store for using nbsps and have been told to switch to #x00A0. Maybe no one cares about Google Play anymore (does it exist?) nonetheless, I have abide by my distributors wishes and not get files rejected.

In Sigil, the #x00A0s get converted into regular spaces. I never ever cross-my-heart-hope-to-die edit in Book View. And I've added #x00A0 to the preserve entities list, all to no avail. Basically, once I'm done editing in Sigil I have to have a separate step of opening in Calibre. And then I can never open the book in Sigil again from that point on. And I really do prefer Sigil.
KevinH is offline   Reply With Quote