Hi Martin > > Just a first observation: If I understand the dvireader script correctly, it > reads all bytes following a "bop" command until the "eop" value 140 is > reached. Since many DVI commands require additional parameters, it's likely > that one of these bytes is 140 as well so that the MD5 sum will be computed > only for a part of the page, i.e. changes in the remaining section wouldn't > be recognized.
The hash is calculated for the area starting from "bop" start + 46 bytes offset, because these are parameters for the pages and they can change. The eop is looked up backwards from the next bop command, so it shouldn't match parameter of another command accidentally. > > Perhaps it's also possible to add the computation and comparison of the > hashes to dvisvgm because it processes the DVI file anyway. I have to think > about this a bit more. It would be certainly nice! Best regards, Michal
