Quote:
Originally Posted by kovidgoyal
All calibre conversions contain @page, that is definitely not the problem. Most likely there is something in the stylesheet the kindle cannot handle and putting a space after @ is causing parsing for the whole stylesheet to fail, thereby allowing the book to work.
|
I realize that @page is used and normally does not cause any problems.
However, in this case the @page was in a comment in a stylesheet with regular text/words following it. The rest of the stylesheet had the @font lines needed to embed the publisher fonts
I'm leaning towards a problem on the Kindle side
I was thinking that the Kindle was not honoring the comments and trying to actually process the @page command unsuccessfully and caused the style sheet to be ignored, and therefore the publisher fonts also in the failed stylesheet were ignored
It appeared to me that adding the space and making it '@ page' would pass the Kindle parser, and then the style sheet would not fail and thus the embedded fonts would be displayable bu using the Kindle Publisher Font.
I want to run a simple test to do a little more testing