MobileRead Forums - Please help with ePub validation errors.

MobileRead Forums (https://www.mobileread.com/forums/index.php)

- ePub (https://www.mobileread.com/forums/forumdisplay.php?f=179)

- - Please help with ePub validation errors. (https://www.mobileread.com/forums/showthread.php?t=149597)

Please help with ePub validation errors.

Hi, I've created an ePub solely for the iBooks store using Adobe Indesign CS5.5 on a PC. I have unzipped and edited some of the html using Notepad+. And I have rezipped.

Using the Pagina validation tool I checked my epub and got these errors:-

Code:

 

WARNING: Book1b.epub: 

   resource OEBPS/fonts/MinionPro-Bold.otf cannot be decrypted 

 

WARNING: Book1b.epub: 

   resource OEBPS/fonts/MinionPro-Regular.otf cannot be decrypted 

 

WARNING: Book1b.epub: 

   item (iTunesMetadata.plist) exists in the zip file, but is not declared in the OPF file

Any idea how to remedy these, and are the warning issues less serious an can they still pass the Apple iBooks check?

.

The first two are a problem with embedding your fonts, I'm not sure if it is the particular font you are using or what. You could wither try and embed no fonts, or use a different one.

The 3rd error happens because you probably loaded you book on your apple device through iTunes. It puts that ".plist" file in there when you do. So either unzip your epub, and delete the file and rezip it. Or re-export it and try and validate it before it sending it though iTunes.

The embedded fonts are encrypted to Adobe's standard since they were exported via InDesign. You'll need to put in unecrypted fonts for the validation to work.

Quote:

Originally Posted by JSWolf (Post 1743908)

The embedded fonts are encrypted to Adobe's standard since they were exported via InDesign. You'll need to put in unecrypted fonts for the validation to work.

or just click off the embed fonts check box in the export to ePub dialogue box.
Myriad is just a sans serif font that you can specify in the CSS.

I've unclicked the option in InDesign and it doesn't embed the fonts. It's fine. Thanks!

Hi guys!

I have the sam eproblem with embeding fonts... I googled and it seems I need to unceck "embed fonts" in indesign when exporting but...

1. I created epub file in Adobe InDesign CC.
2. I made whole bunch of changes on html files and css in Calibre (SVG Vrapper, some text editing in html files, TOC changes... etc)
3. At the end, when I checked it on http://validator.idpf.org some ERRORS epiered. I correct all of them but WARNING: resource 'OEBPS/font/Lato-Regular.ttf' cannot be decrypted stays...

Is there any way to fix it w/out going back to Indd so I could finaly finish this neverending job? I guess some changes in css should do the job but I'm not very good at it.

One more question... Is the WARNING issue reason for rejecting the book for publishing?

Thanks!

InDesign seems to create problems! I would download the free & excellent Sigil software, open the epub in that, and fix it there.

Apple requires books to have pass epubcheck.

Embedding fonts on your own is so easy, just add the file and use the font-face rule to import them...

You get that error I think because the font was obfuscated.

Quote:

Originally Posted by Notjohn (Post 3050389)

InDesign seems to create problems! I would download the free & excellent Sigil software, open the epub in that, and fix it there.

Apple requires books to have pass epubcheck.

nj:

We use INDD daily. It doesn't cause problems any more than does Word. People simply need to actually learn how to use it. Virtually 100% of our White Label work is INDD intake, and of course, all of our own in-house POD work (plus eBooks) is done in it.

Quote:

Originally Posted by odedta (Post 3050476)

Embedding fonts on your own is so easy, just add the file and use the font-face rule to import them...

You get that error I think because the font was obfuscated.

n.b.: don't simply EMBED fonts that require licensing. If you have NOT licensed the font for eBook/app usage, you're putting yourself and your client, presuming one exists, in harm's way, particularly if you are using Adobe fonts. Ensure that you've licensed the font correctly, or replace the foundry fonts with fonts that you are able to license for the use.

Hitch