'It is not your custom to eavesdrop?'
- Page 55
¬‿¬
https://hopfieldiswriting.com/2026/03/03/the-caves-of-steel-reading-tabs-1/
#reading #annotating #thecavesofsteel
'It is not your custom to eavesdrop?'
- Page 55
¬‿¬
https://hopfieldiswriting.com/2026/03/03/the-caves-of-steel-reading-tabs-1/
#reading #annotating #thecavesofsteel
One of the best things you can do while reading is to interact with your book, especially annotating in the margins to jot down ideas and mark up interesting parts of what you just read.
#Reading #Annotating #Marginalia #Books
https://www.scientificamerican.com/article/go-ahead-write-in-the-margins-its-good-for-your-brain/
#tools #DigitalHumanities #collaborating #annotating
From: @aboutgeo
https://vis.social/@aboutgeo/113961403081315903
Better late than never: I finally wrote a proper introduction to liiive! If you work with IIIF image collections and want to collaborate in real time, check it out. 👇 #IIIF #DigitalHumanities https://liiive.now/blog/2025-02-introducing-liiive/
-- EDIT: Added more details --
Question: What is your hardware and software of choice for reading and annotating books/PDFs ? I am looking for opensource or one-time buy options. No renting.
I'm looking for something cross-platform that will work on linux, android and macos.
I sure would love it if #ELAN had a sort of #clipboard akin to #RStudio #snippets. It would make repetitive #annotations so much faster.
Refactoring an .NET application -- How to proceed?
Background: I am sitting with an old (2009) MS #CSharp .#NET Framework 2 desktop application targeting #Windows 7 using #adobe #XMP („Extensible Metadata Platform) SDK toolkit via some no longer supported open source wrapper from a non-existent website for the outdated version 4.1.1 of the Adobe SDK. No CSharp support from Adobe for their SDK available.
Building it for the latest .NET Framework 4.8.1 on Windows 10 and it runs as is (also older Frameworks behave the same on Windows 10), but is not capable of writing XMP meta data back to the filesystem, likely because of some 32-64 bit mismatch between „managed code“ and the #cpp Adobe toolkit.
The application is used for #annotating images in layers on top of images, writing the annotations into JPEG/TIFF files as meta data and probably represents two person years of development work.
It uses both the XMPFiles and XMPCore parts of the XMP Toolkit. I have not been able to identify any third-party libraries supporting both XMPFiles and XMPCore. drewnokes/xmp-core-dotnet (https://github.com/drewnoakes/xmp-core-dotnet) is quite up-to-date, but only supports XMPCore.
I am thinking on how to progress on this.
Boost for visibility most welcome -- Maybe someone even have in-depth XMP experience.
Thanks to @AThielsch for pointing me at https://www.unabridgedopinions.com/blog/i3dwev4ai02t3txk4udo5ok8c6vqdf by Jennie Blake describing her workflow for #reading and #annotating with #obsidianmd.
But the blogpost leaves me with one question: @jnyrose, do you (and of so, how does it fit in your workflow) any kind of reference manager like #zotero?
I've been #annotating a #PDF using #logseq and it has worked well across the first 100 pages or so, but as the number of pages increase it is becoming quite janky. Curious if anyone knows of approaches to circumvent this?
It seems that logseq wants to keep all the annotations in a single file - which is probably part of the problem.
The other part of the problem is that it looks like it wants to keep the highlights visible throughout the book.