Quote:
Originally Posted by geek1011
That was a trade-off I made:
Pros:
- Inline CSS is pretty much guaranteed to work.
- Can be done while transforming HTML.
- Doesn't need to modify the package document.
- No path resolving complexities.
- Won't further break broken books as much (kepubify aims to process broken books as best as possible and not make them worse).
- Not as bad as directly adding styles to elements.
Cons:
- Possibly ambiguous escaping of angle brackets.
- Duplicate CSS in each file.
- Not clean and harder to edit, but this doesn't matter too much (the book is generated and not really going to be edited directly after conversion).
If you have any additional disadvantages for embedded CSS, I'd be happy to consider them.
|
.Embedded CSS could cause the HTML to become larger then the size required for the mobile ePub spec. Also, it's more difficult to edit the CSS.