Repository navigation
Replies: 1 comment
|
There are many issues with this idea, including but not limited to:
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I love Sioyek, but I have a major pain point: any change to the pdf that alters its md5 hash (e.g. changing outline or embedding annotations) will become incompatible with its sioyek annotations in the database upon changing the file path.
Sioyek mitigates some of this issue by caching the hash. However if the path is changed, you have to do something like:
every time a slight but hash-altering change is made, which really decreases usability.
I believe it would be more expedient to hash fixed-size pixmaps of the document pages instead, thus allowing Sioyek annotations to be preserved across many of the common changes.
Not sure how much overhead this would create when opening new pdfs, but caching the hashes should be an acceptable mitigation.
Any thoughts?
All reactions