Hi,
It means I can't type worth a damn. When fixing the dc:type error, I typed "tcontext" instead of "tcontent" and created this error myself. None of the 15 test ebooks I use have dc:type set, so I never caught my typo.
If you have a free moment, could you test the v020 version and see if the new nav code actually works? That is my biggest worry and none of my test cases have a multi-level toc.ncx and so none of the nesting issues were ever apparent.
Thanks,
Kevin
ps: There is now an 0.2.0 version with the typo fix
Quote:
Originally Posted by JonathanMagus
Hi Kevin
I have tried version 0.1.9 with the same two ePUB2 files and this time the conversion process failed, producing an error message, which at a glance looks to me to be the same in both cases. I attach a text file with these in.
Just to be sure there were no other factors involved I reinstated ePUB3-itizer_0.1.8.zip and that works in Sigil as it did before.
Coincidentally I have just been looking at some of the same specifications for a different reason that I may follow up on separately with you sometime.
I am guessing that the error messages will mean more to you than they do to me. Let me know if you need anything more on this.
Regards
Jonathan
|