question about custom validation and normal validation

[tofi86]

I just built the current snapshot from master branch and ran epubcheck:

→ java -jar epubcheck.jar ~/Desktop/Desktop/epubcheck/lorem.epub 
Validating against EPUB version 2.0 - custom validation
WARNING(CSS-022): /Users/tobiasfischer/Desktop/Desktop/epubcheck/lorem.epub/EPUB/lorem.css(2,5): CSS Selector specifies global margin setting.
WARNING(CSS-022): /Users/tobiasfischer/Desktop/Desktop/epubcheck/lorem.epub/EPUB/lorem.css(3,5): CSS Selector specifies global margin setting.
Validating using EPUB version 2.0 rules.
WARNING(HTM-025): /Users/tobiasfischer/Desktop/Desktop/epubcheck/lorem.epub/EPUB/lorem.xhtml(20,57): Non-registered URI scheme type found in href.
ERROR(RSC-012): /Users/tobiasfischer/Desktop/Desktop/epubcheck/lorem.epub/EPUB/lorem.ncx(26,45): Fragment identifier is not defined.

Check finished with errors

epubcheck completed

I didn't use any custom validation flags or files, just the commandline above.

What is the difference between checks in Validating against EPUB version 2.0 - custom validation and Validating using EPUB version 2.0 rules?

I'm just asking because CSS validation previously was a "normal" part of epubcheck...

cheers, toby

[santoch]

Honestly, I don't know. It was emitting that message before I started to work on it. I'll see if I can figure out why it's even saying that its doing anything "custom". I agree with you that this seems wrong.

[tofi86]

Okay, thanks!

[rdeltour]

@santoch any news on that ? are we all OK to remove this "custom validation" message ?

[santoch]

Sure. I have no problems with that.

[rdeltour]

ok, thanks. I'll do it!