MobileRead Forums - View Single Post

shotsky · 07-14-2012, 01:32 PM

Yes, that was a poor choice for a file. The newer ones are all in html5 format now, and they validate.

Still, the link you mention won't work, since the css file is web based, not on users's computers. Anyone can look at those files on the web and will see the result of the css formatting the way it is done. The only other way to do this is to actually embed the .css file into each file, but that would be hugely wasteful, as the @Import command does essentially the same thing, only it is done in the users' browsers on the fly. Lastly, any change I make to the css file now, updates all existing files that use that css.

But the other part of my question is why should Calibre just fail to create an ebook, even if it doesn't use that css? Can't it just bypass the @Import command, especially since it's already 'hidden' in a comment?
Thanks,
John

07-14-2012, 01:32 PM	#3
shotsky Enthusiast Posts: 39 Karma: 10 Join Date: Jul 2012 Device: none	Bad html Yes, that was a poor choice for a file. The newer ones are all in html5 format now, and they validate. Still, the link you mention won't work, since the css file is web based, not on users's computers. Anyone can look at those files on the web and will see the result of the css formatting the way it is done. The only other way to do this is to actually embed the .css file into each file, but that would be hugely wasteful, as the @Import command does essentially the same thing, only it is done in the users' browsers on the fly. Lastly, any change I make to the css file now, updates all existing files that use that css. But the other part of my question is why should Calibre just fail to create an ebook, even if it doesn't use that css? Can't it just bypass the @Import command, especially since it's already 'hidden' in a comment? Thanks, John