Quote:
Originally Posted by rupor
EPUB2 is really complex and it gets worse with EPUB3. So far I have not seen a single software which could flawlessly process all EPUB2 files. The fact that Pocketbook was able to show some particular EPUB file which Sony (which uses Adobe RM SDK) fails to process does not give you a guarantee that with some file it would not happen the other way around 
By the way - in your sample there are several <pre> blocks, but none of them has a single space character... |
In the chapter on the X86 Calling conventions, there's an assembly code listing under the headline cdecl, which has an empty line somewhere in the middle (between "register int ret;" and "ret = callee(1,2,3);"). This line consists of a single space character. That's the culprit, I suppose. At least if I copy that part around, I can make it crash in any chapter.
Which font ... don't know, and cannot look it up either anymore.