View Full Version : Where is line -1 ??


Ref60
02-03-2013, 05:00 PM
I get the following "WARNINGS" when doing ePubCheck ? I have no idea what this is and can't find any google references on how to fix ??

Will this pass the publishers filters or do I need to figure out how to make these Warnings go away ?

Type File Line Position Message
WARNING -1 -1 Token ',' not allowed here, expecting :
WARNING -1 -1 Token ',' not allowed here, expecting :
WARNING -1 -1 Token ',' not allowed here, expecting :
WARNING -1 -1 Token ',' not allowed here, expecting :
WARNING -1 -1 Token ',' not allowed here, expecting :
WARNING -1 -1 The character 'NEWLINE' is not allowed in 'STRING' expressions
WARNING -1 -1 Token ',' not allowed here, expecting :
WARNING -1 -1 Token ',' not allowed here, expecting :
WARNING -1 -1 Token ',' not allowed here, expecting :
WARNING -1 -1 Token ',' not allowed here, expecting :

Aerys
02-05-2013, 05:24 AM
Assuming that your publisher follows standards of using epubcheck/flightcrew then they will see the errors.

WARNING -1 -1 Token ',' not allowed here, expecting :

This is just a guess since you did not post your CSS or HTML but it seems there is a misdeclaration of using a comma "," instead of a colon ":".

DSpider
02-05-2013, 12:18 PM
Check it with Sigil. It usually tells you which line(s) have issues and where it needs tweaking.

mrmikel
02-05-2013, 02:30 PM
-1 may suggest it is up above the <body> statement.

Toxaris
02-05-2013, 03:12 PM
I expect it is an unwanted linebreak, probably in the XML declaration.

_savage
02-05-2013, 03:47 PM
Also notice "The character 'NEWLINE' is not allowed in 'STRING' expressions" which indicates that maybe a closing quote or double-quote is missing somewhere. The -1 can also mean that it's right at the beginning of the file and the scanner (wrongly) hasn't started counting lines/chars yet, or you have so many lines/chars that the scanner overflowed while counting :-)

Can you tell us more about the .epub archive? Where it came from, how big it is etc? It may help to remove files to narrow down which one causes these warnings.