>I'm not sure how you calculate the sha1 hash. I'm using openssl sha1 <<file>>.
>But usually it's calculated from the data fork content. That changes >when you save embedded notes, but not when you save just as PDF >(i.e. not embedded or without notes). (Unless you've converted >notes.) Yes, that's what I'm seeing. The odd thing is that if one takes, say, an rtf and calculates a hash, edits, saves (yielding a different hash), and undoes the edit, the hash is restored to the original value. But the corresponding process with a pdf (adding a Skim note, embedding, and removing) doesn't restore the hash. It's as if the process of editing leaves a "residue". If it's not restored to the original value, it's missed as a duplicate when I use, say FileBuddy or EagleFiler. My tentative solution is to rely on other metadata to identify possible duplicates. humanengr ------------------------------------------------------------------------------ Get your Android app more play: Bring it to the BlackBerry PlayBook in minutes. BlackBerry App World™ now supports Android™ Apps for the BlackBerry® PlayBook™. Discover just how easy and simple it is! http://p.sf.net/sfu/android-dev2dev _______________________________________________ Skim-app-users mailing list Skim-app-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/skim-app-users
