Epub Validator

bimmy · 01-08-2014, 02:04 PM

Hello!

I'm trying to validate an epub file. I've never really understood it. Previously, if I had an error was self explanatory. I would do a search and find the error in the html file. The "line" and "position" columns never match up to the problem. Maybe I'm misinterpreting them? I hope so...because some where in my file I have a stray "p" and a stray "i". Lordy how will i ever find that! Any help on interpreting the "position" of these errors would be wonderful!

Bimmy

DaleDe · 01-08-2014, 02:31 PM

How are you viewing the files that have errors? I suspect that Notepad++ would be a good choice to look at the raw files and it shows line numbers on the left size. For epub you would need to take the ePub apart using a tool like zip unpack it. Note that epub check notes the location where it detected the error. If the error is the absence of a closing tag then the detection will be far from the actual error.

bimmy · 01-08-2014, 03:12 PM

I'm viewing in jedit.

bimmy · 01-08-2014, 03:30 PM

just viewed in Notepad++ like suggested and line numbers are the same.

theducks · 01-08-2014, 03:49 PM

Also note that in some error reports:
The line means Before this point.
That point being where the error became obvious: say the <p> begins a 500 word paragraph. The closing </p> may be many screen lines down
The validator ran into a New <p> (the line and col) .
You can't nest <p> tags: an obvious error

Sometimes you need to backtrack. It all depends on the EXACT error message

bimmy · 01-08-2014, 03:57 PM

well, I found my first errors. I've gotten rid of errors at line 11, 12, 13. they were actually at line 78,79,80. Extrapolating an 80 line difference didn't work. My next errors were at 72, 73 and there was nothing there.

bimmy · 01-08-2014, 05:05 PM

well i went through line by line searching "i>". While all the remaining errors were said to be at lines in the seventy range, I actually found them in and around the 2000 range. Sucks. Why don't the line numbers match up for me?

mrmikel · 01-08-2014, 07:41 PM

It is because they are processed from the top, and that is the point at which there weren't enough ends to go with the beginnings. That is often at the end of the document for something like paragraph markers.

It can be easier to start at the top and look for ends to go with beginnings visually by paragraph or phrase. There is not a way to parse it backwards from the end...I asked.

bimmy · 01-08-2014, 09:11 PM

LOL! Sounds like you have experience! But I've also experienced errors where I've mispelled something like "chapter" and put "chater" or something. It's easy enough to find because I can search for the mispelling. But the line indicated was still not correct.

GrannyGrump · 01-09-2014, 01:49 AM

If you use Sigil -- Although the Flight Crew validator in Sigil is not as thorough as other validators, sometimes it is possible to double-click the line number to take you directly to the error. (But often, it too gives wrong line numbers.)

elibrarian · 01-09-2014, 04:09 AM

If possible, post the file (no copyrighted material, though!) - it wil probably be easier to help then.

It is important that you (if at all possible) find the errors one at a time, from the top of the file, as one badly placed or missing tag in the beginning of the file is able to generate two million error-messages (well, a lot

)

Another tip, which helped me a lot in the start: Try to unzip the epub and run the (x)html file(s) through the W3C validator at http://validator.w3.org/#validate_by_upload - set the "More Options" to "Verbose output".

Hope this helps,

Regards

Kim

mrmikel · 01-09-2014, 07:21 AM

It might help to put on your thinking cap for a sec instead of banging away at it. Is there any pattern to your previous errors that might suggest what is going on?

If they really are random, then you just have to look and look, but if you put them in there, you may have done them something other than randomly.

01-08-2014, 02:04 PM	#1
bimmy Junior Member Posts: 6 Karma: 10 Join Date: Jan 2014 Device: kindle	Epub Validator Hello! I'm trying to validate an epub file. I've never really understood it. Previously, if I had an error was self explanatory. I would do a search and find the error in the html file. The "line" and "position" columns never match up to the problem. Maybe I'm misinterpreting them? I hope so...because some where in my file I have a stray "p" and a stray "i". Lordy how will i ever find that! Any help on interpreting the "position" of these errors would be wonderful! Bimmy

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Does epub validator work?	jacksion5	ePub	4	12-10-2013 09:41 AM
epub validator	TracyEire	ePub	4	12-06-2013 05:12 AM
ePub validator	fifisailing	ePub	6	07-31-2012 09:32 AM
Epub Validator?	Latch	Kobo Reader	0	10-20-2011 09:07 AM
epub validator	fiona86	Conversion	2	06-24-2011 11:34 AM

01-08-2014, 02:31 PM	#2
DaleDe Grand Sorcerer Posts: 11,470 Karma: 13095790 Join Date: Aug 2007 Location: Grass Valley, CA Device: EB 1150, EZ Reader, Literati, iPad 2 & Air 2, iPhone 7	How are you viewing the files that have errors? I suspect that Notepad++ would be a good choice to look at the raw files and it shows line numbers on the left size. For epub you would need to take the ePub apart using a tool like zip unpack it. Note that epub check notes the location where it detected the error. If the error is the absence of a closing tag then the detection will be far from the actual error.

01-08-2014, 03:12 PM	#3
bimmy Junior Member Posts: 6 Karma: 10 Join Date: Jan 2014 Device: kindle	I'm viewing in jedit.

01-08-2014, 03:30 PM	#4
bimmy Junior Member Posts: 6 Karma: 10 Join Date: Jan 2014 Device: kindle	just viewed in Notepad++ like suggested and line numbers are the same.

01-08-2014, 03:49 PM	#5
theducks Well trained by Cats Posts: 29,801 Karma: 54830978 Join Date: Aug 2009 Location: The Central Coast of California Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A	Also note that in some error reports: The line means Before this point. That point being where the error became obvious: say the <p> begins a 500 word paragraph. The closing </p> may be many screen lines down The validator ran into a New <p> (the line and col) . You can't nest <p> tags: an obvious error Sometimes you need to backtrack. It all depends on the EXACT error message

01-08-2014, 03:57 PM	#6
bimmy Junior Member Posts: 6 Karma: 10 Join Date: Jan 2014 Device: kindle	well, I found my first errors. I've gotten rid of errors at line 11, 12, 13. they were actually at line 78,79,80. Extrapolating an 80 line difference didn't work. My next errors were at 72, 73 and there was nothing there.

01-08-2014, 05:05 PM	#7
bimmy Junior Member Posts: 6 Karma: 10 Join Date: Jan 2014 Device: kindle	well i went through line by line searching "i>". While all the remaining errors were said to be at lines in the seventy range, I actually found them in and around the 2000 range. Sucks. Why don't the line numbers match up for me?

01-08-2014, 07:41 PM	#8
mrmikel Color me gone Posts: 2,089 Karma: 1445295 Join Date: Apr 2008 Location: Central Oregon Coast Device: PRS-300	It is because they are processed from the top, and that is the point at which there weren't enough ends to go with the beginnings. That is often at the end of the document for something like paragraph markers. It can be easier to start at the top and look for ends to go with beginnings visually by paragraph or phrase. There is not a way to parse it backwards from the end...I asked.

01-08-2014, 09:11 PM	#9
bimmy Junior Member Posts: 6 Karma: 10 Join Date: Jan 2014 Device: kindle	LOL! Sounds like you have experience! But I've also experienced errors where I've mispelled something like "chapter" and put "chater" or something. It's easy enough to find because I can search for the mispelling. But the line indicated was still not correct.

01-09-2014, 01:49 AM	#10
GrannyGrump Obsessively Dedicated... Posts: 3,200 Karma: 34977896 Join Date: May 2011 Location: JAPAN (US expatriate) Device: Sony PRS-T2, ADE on PC	If you use Sigil -- Although the Flight Crew validator in Sigil is not as thorough as other validators, sometimes it is possible to double-click the line number to take you directly to the error. (But often, it too gives wrong line numbers.)

01-09-2014, 04:09 AM	#11
elibrarian Imperfect Perfectionist Posts: 464 Karma: 724664 Join Date: Dec 2011 Location: Ølstykke, Denmark Device: none	If possible, post the file (no copyrighted material, though!) - it wil probably be easier to help then. It is important that you (if at all possible) find the errors one at a time, from the top of the file, as one badly placed or missing tag in the beginning of the file is able to generate two million error-messages (well, a lot ) Another tip, which helped me a lot in the start: Try to unzip the epub and run the (x)html file(s) through the W3C validator at http://validator.w3.org/#validate_by_upload - set the "More Options" to "Verbose output". Hope this helps, Regards Kim

Advert

Advert

01-09-2014, 07:21 AM	#12
mrmikel Color me gone Posts: 2,089 Karma: 1445295 Join Date: Apr 2008 Location: Central Oregon Coast Device: PRS-300	It might help to put on your thinking cap for a sec instead of banging away at it. Is there any pattern to your previous errors that might suggest what is going on? If they really are random, then you just have to look and look, but if you put them in there, you may have done them something other than randomly.