A plugin to enhance PDF annotating.
Table of Content
Import Annotations from pdfs you have uploaded into your graph.
Upload one or multiple PDF files including any embedded annotations.
Embed annotations you create in the builtin reader directly to your pdf document.
Three commands are available (demo below)
PAM: Import PDF Annotations(can be invoked from the block context menu)PAM: Upload PDF with Annotations(available as a slash command)PAM: Embed PDF Annotations(can be invoked from the block context menu)
-
PAM: Import PDF Annotations - This command will import annotations from the current block by populating the annotaions page usually
hls_filename.mdin the/pagesfolder and create a metadata filefilename.ednin the/assetsfolder -
PAM: Upload PDF with Annotations - This slash command will allow you to select multiple pdfs wish will be uploaded to logseq alongside their annotations
-
PAM: Embed PDF Annotations - This commands embeds/export annotations created with the built-in reader (annotations that do not have the
diffMarkeras a property).-
The defualt behaviour of this command is to replace the file in your asset folder; unless you've checked the
exportembedded annotation to external fileoption in the plugin setting, in which case you are prompted to save a copy of the file in a desired location -
The embed function is quite useful if you sync your notes from PC.
-
When you open your pdf in the logseq mobile app your highlights will be available if you have embedded them
-
-
diffMarker : An identifier which is used to set a block property for annotations and files modified by the plugin. Default value is
pam -
checkDuplicates: Checks for duplicate annotations when importing annotations, depends on the
diffMarkerproperty above. Checked by default. -
overWrite: will cause the plugin to overwrite the current annotation metadata for the pdf file. (this is the
hls_pdfFileName.mdfile). Not Checked by default. -
export: if checked will prompt to save a copy of the pdf file in another location when embedding annotations.
-
ISSUES
- This plugin has been tested to work on the windows logseq desktop app.
- If you run into an issue please report as an issue, request a feature or make a PR
-
File Access
-
You cannot select well-known directories (Documents, Desktop, Downloads, Pictures, Music, Videos, etc) as your graph directory. You can however pick a sub directory of any of them.
-
If you do select any of these directories, there's a possibility that file acess will be broken. (A "Directory acess cancelled" warning will be displayed). `Reload the plugin to fix this.
-
See: Stack Overflow file access API broken for additional information on this.
-
-
This extension depends on the The File System API — with extensions provided via the File System Access API to access files on the device file system — allows read, write and file management capabilities. However, this access is not persisted across session. If you reload the extension or restart logseq, the extension will request permission to access your graph folder again.
-
This Plugin assumes the folder structure below, as such absolute links are not supported. Your PDFs are stored and retrieved from the
/assetsfolders. -
If you've used an extension to load a PDF from a directory other than the /assets folder. The extension won't be able to find your pdf file.
-
-
Want to Hide the diffMarker property attached to all annotations and appended to the file label ?
-
Performace
- The plugin may take longer to process large files with a lot of annotations.
-
Support for JSON, XFDF & FDF annotation storage
- No support at the moment.
-
Supporting for other types of Annotations
- The plugin only supports higlights now. Future update may enable the ability to import as highlights all annotations of the subtype "Text markup annotations" as defined by the PDF spec 1.
The plugin depends on the MuPDF.js library which is released under the the AGPL v3.0 and PDF.js under the Apache 2.0 licence.


