Quote:
Originally Posted by kovidgoyal
Since azw3 does not support the epub namespace or indeed the epub spec in any form, that's hardly surprising.
|
Didn't mean to imply it was surprising. I was more just creating a record of the information I'd found. I'm not very good at remembering all these sort of details otherwise.
Quote:
Originally Posted by kovidgoyal
Ah the innocence of youth. The chances of encountering a valid XML file, let alone a valid XHTML file in the wild are about as high as the chances of encountering valid XHTML on the web. So if you want to use epub:type the onus is on you to make sure that the file you are outputting somehow magically becomes valid XML from tag soup. calibre has nearly 10,000 lines of code dedicated to the task of taking tag soup and outputting valid XML. SO unless your book has been previously processed by calibre and then not further processed by anything else, you are likely to be out of luck.
|
Well, this is for books where I've manually edited in the page breaks so I can actually expect that calibre has been the processor. Indeed, since amazon uses a side-along file I don't expect them to be there otherwise.
Quote:
Originally Posted by kovidgoyal
The epub standard does not use span tags. The standard simply declares an attribute that can be placed on (almost) any tag. And the selectors I am referring to are selectors like first-child, last-child, nth-child which will break if you change the number of children by inserting a new tag.
|
I'm referring to
this part of the standard which do specify that page breaks should use span or div tags (I missed that div tags could also be used).
Anyway, it looks like I've got enough information to get to work now.