FlightDeck ePub check errors

Gregory Perry

This topic has 2 replies, 1 voice, and was last updated 3 years, 1 month ago by Diane Serpa.

Viewing 2 reply threads

Author

Posts
- October 27, 2016 at 2:44 am #89344
  
  Gregory Perry
  Member
  
  I’ve used FlightDeck to check an ePub I exported from InDesign. It detected a number of errors I need assistance with. The first is this…
  
  These files include inline styles.
  * OEBPS/cover.xhtml
  Content and presentation should be separate in EPUB files. Inline styles are difficult to edit easily and are not the best approach. We recommend that you move all of your styles to an external stylesheet.
  
  Here’s the code from my OEBPS/cover/xhtml file:
  [CODE]<?xml version=”1.0″ encoding=”UTF-8″ standalone=”no”?>
  <!DOCTYPE html>
  <html xmlns=”https://www.w3.org/1999/xhtml” xmlns:epub=”https://www.idpf.org/2007/ops”>
  <head>
  <title>cover</title>
  </head>
  <body>
  <div style=”text-align:center;” epub:type=”cover”>
  
  </div>
  </body>
  </html>[CODE]
  
  How do I change this code to fix the error listed above. The page should only have an image so I’m not clear why it even has a heading?
  
  Second error message is also puzzling to me.
  [Beginning of Error message] Text color should not be set to black using CSS, because the text will be unreadable in Night Reading Mode on some devices. This EPUB has the following CSS rules which set text to black. [End of error message]
  The reason this one is confusing is because all the paragraph styles it mentions are not set to black. In fact they are set to registration in the paragraph styles. Therefore it seems indesign is overwriting the styles when it exports to ePub or at least that’s the best I can figure. How can this be corrected?
- November 3, 2016 at 3:46 pm #89585
  
  Aaron Troia
  Participant
  
  Hey Gregory,
  
  First error: I haven’t had any issues with this erring out in ePubCheck nor have I received any complaints about my ePubs throwing errors in iTunes, it might just be an overly cautious part of the FlightDeck script that is catching this, I think you should be fine. I would email FlightDeck directly and bring this up.
  
  Second error: just remove the “color:#000000” line throughout your CSS. InDesign is probably setting the text to black even though you have the text set to registration.
  
  Aaron
- March 18, 2021 at 2:59 pm #14337523
  
  Diane Serpa
  Member
  
  Can you at least speak to why it sometimes happens and sometimes does not?
  And how to fix it in code?
Author

Posts