The PKMS software logseq is capable of viewing and annotating PDF files.
These annotations are stored in markdown files with this naming convention:
hls__FILENAME_TIMESTAMP_0.md
Where FILENAME is the name of the PDF being annotated, minus its extension, with special characters converted to underscores, and TIMESTAMP is what appears to be a unix timestamp.
These files contain file and file-path properties (in logseq speak) that contain the a link to the PDF file with anchor text representing its full, unstripped filename (minus path), and plain text that is identical to the anchor for the prior link.
Following these properties are [:span] sections, one per annotation. Each has the following properties:
ls-type - example: annotation
hl-page - integer page number, simple
hl-color - string colour of highlight
id - (question: is this the logseq graph ID of the datom that will refer to this annotation, or some internal annotation ID?)
The PKMS software logseq is capable of viewing and annotating PDF files.
These annotations are stored in markdown files with this naming convention:
hls__FILENAME_TIMESTAMP_0.md
Where FILENAME is the name of the PDF being annotated, minus its extension, with special characters converted to underscores, and TIMESTAMP is what appears to be a unix timestamp.
These files contain
file
andfile-path
properties (in logseq speak) that contain the a link to the PDF file with anchor text representing its full, unstripped filename (minus path), and plain text that is identical to the anchor for the prior link.Following these properties are
[:span]
sections, one per annotation. Each has the following properties:ls-type
- example: annotationhl-page
- integer page number, simplehl-color
- string colour of highlightid
- (question: is this the logseq graph ID of the datom that will refer to this annotation, or some internal annotation ID?)hl-type
- example values: areahl-stamp
- a timestamp