Thread: Sigil’s Future Direction (Post 0.4.x)
View Single Post
Old 09-06-2011, 04:50 PM   #37
theducks
Well trained by Cats
theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.
 
theducks's Avatar
 
Posts: 31,149
Karma: 60406498
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
Quote:
Originally Posted by charleski View Post
One thing I know for certain is that is we were to introduce that then we'd get people complaining that the book looked fine on their PC, but ended up using a completely different font on their reader. It just introduces more possibility for confusion.

As it is right now, Sigil's Book View follows the rules for default handling of fonts that are specified in the standards - what you're seeing are the defaults built into Webkit. If you don't specify anything in the css you're telling the User Agent to decide for itself, and Sigil reflects that. Adding user preferences for this sort of thing would break the WYSIWYG model and that's too high a price to pay for something that the user can already do very easily by specifying their preference in the correct place, which is in the css.
Actually, this issue exists if non-common fonts are not embedded. The device uses the fall-back, where the font may have been available to the PC/Sigil.
theducks is offline   Reply With Quote