Incorrectly reporting an error

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1. It gives what I believe is a false error on the opf file if the date is 
2010-12-1 - the error:

The <date> element's value is "2010-12-1", which is not a valid date format.

What is the expected output? I expected it to be no error. 2010-11-31 did not 
generate an error. 

Which is to say that what had no errors yesterday has one error today. This on.

What version of the product are you using? On what operating system?
0.7.1
Ubuntu 10.10

Nice tool.

Original issue reported on code.google.com by capt.eme...@gmail.com on 1 Dec 2010 at 5:53

GoogleCodeExporter commented 9 years ago

You are incorrect. "2010-12-1" is not a valid date format; the date you wanted 
should be represented as "2010-12-01".

Original comment by Strahinja.Markovic@gmail.com on 1 Dec 2010 at 5:58

Changed state: Invalid

GoogleCodeExporter commented 9 years ago

I'm sorry about that. Hard to believe that they can't handle something so  
simple. Thanks for the catch.

I'm releasing a bunch of educational ebooks for kids as CC BY that used to  
be copyrighted. Your tool is a lifesaver.

brad

Original comment by capt.eme...@gmail.com on 1 Dec 2010 at 6:22

Sigil-Ebook / flightcrew

Incorrectly reporting an error #17