View Single Post
Old 07-19-2017, 08:31 PM   #5
st_albert
Guru
st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'
 
Posts: 698
Karma: 150000
Join Date: Feb 2010
Device: none
Hey, thanks for your quick response and fix.
I can fully understand how the parser gets confused. When I was a young pup learning Algol on a Burroughs B5500, we used to have a game: How many compiler errors could you generate with a single typo in the source code? Hint: leaving off a semicolon at the end of a statement was a good move.
Seems like the same kind of problem is at work here. Without the closing quote, how does the parser know when the end of the quoted text actually occurs? So, even if the solution isn't precisely correct, it at least calls attention to the error and allows one to actually fix the problem.

(For me, using the metadata editor is not nearly as good a solution, since I'm dealing with inserting at least a dozen or more entries, which are *usually* provided, well formed, in a text file that only needs to be copied into content.opf. I've done this close to a hundred times, and this is the first time I've run into this error. So next time, I'll know what to look for.)

Kudos!

Albert
st_albert is offline   Reply With Quote