Quote:
Originally Posted by ProDigit
The only devices I really looked at making ebooks on, where the Kindle Paperwhite, Kobo H2O, Sony PRS-505, and Jetbook Color.
All of them allow some basic change of fonts, sizes, line spacing, and in some cases margin sizes, and paragraph spacing.
In case of JSWolf's last example, is a good reason to use CSS, using multi font types in one document, ...
But many books only use one font. Especially older books (those in public domain), with only variations either bold or italic text, which can easily be done in HTML.
|
It's not just the use of multiple fonts. Sis you notice the section with the sans-serif font? Did you see how it is offset from the regular text and without the CSS, that offset is lost so it becomes a run-on mess.
As for the different Readers you mentioned, you did not test them properly because if you did, you'd notice that the 505 does NOT allow changing fonts. The only way to change the fonts used in the 505 is to embed them.
Anyway, let's say you add all your styling code to the XHTML files and then you decide you want to make a change in the formatting? You would have to find every occurrence of that style and change it. In CSS, you just change the relevant class and you are done.
Really, CSS makes life so much easier when designing the eBook. What is it you have against CSS? Why do you want to make life much harder on yourself?