View Single Post
Old 12-25-2008, 02:52 PM   #21
Jellby
frumious Bandersnatch
Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.
 
Jellby's Avatar
 
Posts: 7,554
Karma: 19500001
Join Date: Jan 2008
Location: Spaniard in Sweden
Device: Cybook Orizon, Kobo Aura
Quote:
Originally Posted by HarryT View Post
Yes, I agree with you, but I'm not sure what point it is that you're trying to make. As a book creator, all I care about is whether or not I can use CSS in my "source" files. What difference does it make to me whether it's the program that creates the book or the program that displays the book that "understandard" the CSS?
Then Mobipocket supports Word, PDF, OpenOffice, nested tables, SVG and whatnot... Some way or other you can find a way to convert any of these to Mobipocket, even if you lose some features.

I do correct Mobipocket files if I can (and if I cannot make the original author to correct them).

Besides, ideally, supporting CSS would mean that there could be a way to override the book-specific CSS with reader-specific CSS (say, I could change "em { font-style: italic }" to "em { font-weight: bold }", or set "img { display: none}").
Jellby is offline   Reply With Quote