View Single Post
Old 04-19-2013, 12:40 PM   #8
SusanM
Bemused by possibilities
SusanM ought to be getting tired of karma fortunes by now.SusanM ought to be getting tired of karma fortunes by now.SusanM ought to be getting tired of karma fortunes by now.SusanM ought to be getting tired of karma fortunes by now.SusanM ought to be getting tired of karma fortunes by now.SusanM ought to be getting tired of karma fortunes by now.SusanM ought to be getting tired of karma fortunes by now.SusanM ought to be getting tired of karma fortunes by now.SusanM ought to be getting tired of karma fortunes by now.SusanM ought to be getting tired of karma fortunes by now.SusanM ought to be getting tired of karma fortunes by now.
 
SusanM's Avatar
 
Posts: 58
Karma: 480244
Join Date: Jul 2012
Device: iPad3, Kobo
Quote:
Originally Posted by curiousgeorge View Post
it appears that your meta is for an epub 3.0 file and the validation tool you're using only validates up to 2.0. This is an example of why many companies will not take full epub 3.0 files. You can implement certain epub 3.0 criterias but coding fully for epub 3.0 will not be backwards compatible and will render your epub invalid.
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.
SusanM is offline   Reply With Quote