I also tried going through the steps of generating an epub file by a different process. Calibre assumed my file was an epub 3 and will (so far as I can tell) only convert it to an epub 3 document, so that was sort of pointless. Not knowing whether Pages had created a version 2 or 3 epub (how can you tell?), I loaded the epub into Calibre and set up a conversion from epub to epub-I thought I might be able to convert it from one to other and retry the upload. I wondered about the epub 2 vs epub 3 question. Just hope it doesn't cause any sort of issue further down the road to publication, as with the application of DRM by the distributing sites. Your experience might suggest that the problem is actually with the epub checker's failure to recognize some aspect of Apple's META items. COULD NOT START THE EPUB CHECKER CODEBut the error code shows up in the epub test the same as before. It uploaded and when redownloaded it was still intact and still working perfectly on Overdrive, Bluefire, Kobo, and iBook reading apps. The help people at that site directed me to this epub testing software, which is where I learned about the error.Īfter wasting many hours trying to understand that error code as the reason for the upload failure (and panicking because I thought maybe some proprietary coding makes it so Pages epubs will ONLY upload to iBooks), on a whim, I reduced the file name to letters with no spaces. The only reason I even know about the error code is that initially the test file wouldn't upload on one of several sites I plan to distribute on (Kobo) other than iBooks. That's interesting (although I've never actually tried altering an OPF file). The older e-paper Nooks, in my experience, are even worse. They have very limited EPUB support as far as features go, so it's definitely worth testing even if there are no errors-a lot of things iBooks will display just fine a Kindle will choke on. You should be able to view it in the Kindle application, and there is also a Kindle simulatior available from Amazon that lets you see how an e-paper Kindle will render books without having to buy one. Kindle is far and away the most popular reader, so try it with that and see if it comes out looking how you expect. However, the best way to find out if it's going to work right is to test it. Regardless, if the sites accept it, there's a good chance it is okay DRM, at least, isn't going to change anything-only if an e-reader changes its EPUB parser at some point and breaks something, which seems unlikely. It could also be something as simple as Pages generating a file that is marked as an EPUB v2 file but that uses EPUB v3 features (I know my book was intended to be v3, and I could have inadvertently used headers for v2). COULD NOT START THE EPUB CHECKER FREEI was using a free Java-based checker myself, and the fact that I managed to clear up the error indicates to me (unless I'm remembering wrong or misunderstood what fixed it in my case) that it's probably not technically the EPUB checker's failure to recognize the Apple META property more accurately, it's that the XML dictionary the file is referencing doesn't include the Apple items in it, so the EPUB checker is correctly complaining about it. I can imagine a site running a standard EPUB verifier, and if any errors at all are thrown rejecting the file, but practically speaking an unknown META tag (what's causing this error) should be ignored by the parser and therefore by definition be harmless. Based on that, it does sound like the sites you were having problems with had to do with filenames, not this error.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |