Quote:
Originally Posted by user_none
<rant> One thing in particular I keep hearing is the ability to set a default font in book view. Sigil is not a reading app, if you want a particular font then specify it in the file. Also, the good thing about a standard default font is it is very easy to tell if the file has specified a font.
</rant>
|
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.