View Single Post
Old 04-23-2013, 09:35 AM   #10
curiousgeorge
Connoisseur
curiousgeorge began at the beginning.
 
Posts: 53
Karma: 10
Join Date: Aug 2012
Location: Nashville, Tn
Device: ipad, Kindle Fire
Quote:
Originally Posted by SusanM View Post
The validator that srascal is using is the current standard and is for the current standards for EPUB2/EPUB3. Blue Griffin has a more advanced validator for EPUB3 only at http://www.bluegriffon-epubedition.com/BGEV.html but it is not free. I have no idea if this one validates the code below and even if it does, whether retailers would accept it as many of the readers accept only partial ePub3 formatting.

<dc:title id="t1">A Dictionary of Modern English Usage</dc:title>
<meta refines="#t1" property="title-type">main</meta>
<dc:title id="t2">First Edition</dc:title>
<meta refines="#t2" property="title-type">edition</meta>

The above does not validate in IDPF's own validator.
doesnt matter what validator HE uses.. If an e-retailer says your file is invalid that's what it is and I'm telling you I know four off the top that will not except his epub because of the epub 3.0 metadata. Not trying to be rude but thats just how this business works. They would rather be backwards compatible than updated on current validation and because of that they do not use updated validation till it is solid and not in what they consider as beta. I see no reason to go with Blue Griffin because there are many free solutions out there and with only validatoning to 3.0 spec will prevent your content from reaching many retailers.

Last edited by curiousgeorge; 04-23-2013 at 09:39 AM.
curiousgeorge is offline   Reply With Quote