Reply To: ePub vs IDCC (InDesign Creative Cloud)

The problem is that if you enter a new Unique ID this will be added to the metadata and used for the TOC.NCX but InDesign will still leave around the original UUID in the metadata.

This is what content.opf will look like:
<dc:identifier id=”bookid”>urn:uuid:8B0605B1-0129-4B8D-B3AC-AB4D142F5C0D</dc:identif ier>
<dc:identifier id=”ISBN”>urn:isbn:978-0-9729563-1-4</dc:identifier>
toc.ncx will look like:
<meta name=”dtb:uid” content=”978-0-9839980-3-7″ />
This causes problem during EPUB validation – the TOC.NCX needs to match the <identifier> which is declared to be “bookid”.

However, simply removing the “bookid” <identifier> would not be right in case of font embedding. If you embed fonts then the <identifier> with the “bookid” is the one which is used to obfuscate the fonts and if you remove it afterwards (or change the <identifier> with the “bookid” then the reader won’t be able to successfully de-obfuscate the fonts.

So the workaround for EPUB validation would be to edit toc.ncx file in EPUB and add this line instead of the one entered by InDesign above:
<meta name=”dtb:uid” content=”urn:uuid:8B0605B1-0129-4B8D-B3AC-AB4D142F5C0D” />

I hope this explains your query.

Regards,
Pooja