View Single Post
Old 06-29-2013, 02:03 PM   #25
st_albert
Guru
st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'
 
Posts: 698
Karma: 150000
Join Date: Feb 2010
Device: none
Quote:
Originally Posted by Notjohn View Post
I had a related experience with entities. In a book with block extracts in Courier font, I was dismayed to see that in book view Sigil rendered bullets and en dashes as generic black blocks. As it happens, this book was only for the Amazon Kindle platform, so I uploaded the epub to the KDP and let it convert. I was pleased to see that, pace book view, the bullets and en dashes rendered correctly, so I published it without "fixing" the errors.

But the question still nags me: if I had uploaded the epub to Barnes & Noble etc., which would have won out, the html entity for bullet or the black blob?

I use named entities. Would numerical entities have made Sigil happier?
In my experience, the Qt-webkit stuff that Sigil uses for the book view display is not a reliable indicator of what it will look like on other platforms. Why not try out the epub in Adobe Digital Editions, or in some other readers, and see what happens?
st_albert is offline   Reply With Quote