MobileRead Forums - View Single Post

moriakaice · 09-17-2010, 12:48 PM

Ok, I'll admit I haven't read through this topic, but... Can we have calibre to output a correct <date> element in the content.opf in ePUB output? The specs expect it to be 4-digit year, then optional 2-digit month and then optional 2-digit day (AKA YYYY[-MM[-DD]]).

So, instead of something like:

Code:

<dc:date>2010-09-15T22:00:00+00:00</dc:date>

Can we get:

Code:

<dc:date>2010-09-15</dc:date>

It should be even simpler and make calibre ePUBs conform the specs (at least some part of it).

The other thing is that epubcheck doesn't like the <br> tag just before the </body> that calibre adds. Maybe this could be fixed as well? Putting it in the <p> tag solves the problem.

09-17-2010, 12:48 PM	#799
moriakaice Memento Mori Posts: 36 Karma: 10 Join Date: Apr 2007 Device: eClicto, iPad WiFi, Kindle 3 WiFi	Ok, I'll admit I haven't read through this topic, but... Can we have calibre to output a correct <date> element in the content.opf in ePUB output? The specs expect it to be 4-digit year, then optional 2-digit month and then optional 2-digit day (AKA YYYY[-MM[-DD]]). So, instead of something like: Code: <dc:date>2010-09-15T22:00:00+00:00</dc:date> Can we get: Code: <dc:date>2010-09-15</dc:date> It should be even simpler and make calibre ePUBs conform the specs (at least some part of it). The other thing is that epubcheck doesn't like the <br> tag just before the </body> that calibre adds. Maybe this could be fixed as well? Putting it in the <p> tag solves the problem.