Quote:
Originally Posted by DiapDealer
Why do you insist on saying stuff like this? MOBI is no more predisposed to being "full of garbage code" than any other format is. Not supporting CSS means that there will be much more in the way of inline attributes—spans and font tags and the like. It certainly doesn't look as good; I'll grant you that. And while that's unfortunate and not as "pretty" to look at or as "editable" as xhtml with some subtly applied CSS might be, it's not "garbage code," it's the code that's required to make a MOBI function.
Garbage code is garbage code... and no format is immune or predisposed to it. They're all equally susceptible.
|
I know every eBook format can be full of garbage code. Just take a look at a lot of the ePubs from Smashwords. There, your garbage in, garbage out.
But more often when I look at the code of a Mobipocket from a BPH vs an ePub from a BPH, the ePub is OK and the Mobipocket can easily be a mess.