Thread: Kobo Bug thread
View Single Post
Old 04-18-2018, 02:24 AM   #980
chrisridd
Guru
chrisridd ought to be getting tired of karma fortunes by now.chrisridd ought to be getting tired of karma fortunes by now.chrisridd ought to be getting tired of karma fortunes by now.chrisridd ought to be getting tired of karma fortunes by now.chrisridd ought to be getting tired of karma fortunes by now.chrisridd ought to be getting tired of karma fortunes by now.chrisridd ought to be getting tired of karma fortunes by now.chrisridd ought to be getting tired of karma fortunes by now.chrisridd ought to be getting tired of karma fortunes by now.chrisridd ought to be getting tired of karma fortunes by now.chrisridd ought to be getting tired of karma fortunes by now.
 
chrisridd's Avatar
 
Posts: 983
Karma: 2209358
Join Date: Nov 2011
Location: London, UK
Device: Kobo Aura, Kobo Aura ONE, PocketBook InkPad Color 3
Quote:
Originally Posted by Rev. Bob View Post
That's more common than you might think, and it has a long history. Somewhere along the line, some people got the idea that the semicolon terminator character for HTML entities was optional, and "forgiving" web browsers were coded to correct for that mistake - just as they were to handle improperly nested tags and other common issues.

That's what you're seeing here. An ampersand, the letters "quot", and a semicolon constitute the HTML entity for the " character. I haven't looked at the firmware, but I'd wager that the Annotations module uses the web browser's rendering engine, and that that engine is designed to forgive dropped semicolons. Making the engine stricter can come at the price of exposing bad code in other books as being bad.
I agree, the annotations screen is using a more forgiving parser than the one in the main reader.

That's still a bit (not sure how much) of a concern. As the main reader's parser is apparently correct here, I don't see why the annotation window can't be at least as strict.
chrisridd is offline   Reply With Quote