>if archive.org scans in a hardback with its ISBN, what do I use for the scanned pdf?
The scanned pdf just doesn't have an ISBN. ISBNs are assigned by publishers to products for inventory management. That's it. If archive.org scans a book, it's not a product that needs inventory control.
I need unique identifiers. And I disagree. For me, the scan of a book keeps the same ISBN as the printed book that was scanned (when it has an ISBN at all). No other sensible alternative really exists. I also believe Open Library catalogs them the same (since they are archive.org too, and doing much of the scanning).
You may need a unique identifier. You may use the isbn if you like. No one will stop you from doing that. But no isbn-issuing entity has applied an isbn to that file.
Is there a way to do the equivalent of Word's 'track changes' feature in Vim/Neovim? As an editor who reviews manuscripts in Word, I want to be able to make edits, have the author review/approve them, then clean up the result into a file that goes to the typesetter. If I could do that, then a plugin like this becomes potentially more useful to our workflow.
A source control tool such as git or mercurial will solve this. Any collaborator who uses vi should have no issues with a git/hg workflow for managing changes.
As someone who uses Git for technical writing and Word's revision system for fiction that goes back and forth with an editor, I mean, sure, it's sort of a merge request, but you need to place a higher value on the "goes back and forth with an editor" part of the requirement than I think you are. :) An editor suggests changes, sometimes by editing directly and sometimes by leaving comments, that the author can accept, delete, or modify, right? If we're talking about technical writing that's already in a Git repo, then using a PR review system like GitHub's is an acceptable substitute. If we're talking about somebody sending a story to the New Yorker, we're not.
I'm definitely not saying established organizations should change their workflows to "just use git" or something—word processors already offer these features, and the workflow at the New Yorker is already tailored around the affordances of Word documents.
The underlying data model, though—passing around diffs and comments, tweaking sets of modifications before applying them—is the same. You could put together a decent editing workflow around git (although maybe the UI would need to be different from what we use for code). Version control is editing, is my point.
What, and do seperate commits and merges for every comma and dangling modifier? That makes no sense. In addition, there needs to be comments and queries.
Well, no, no more than you would package each comma or dangling modifier into a separate change-tracked .docx. The underlying unit of revision here is a full change set, rather than an individual change.
There are no good options for grandma these days. I've been helping my 85-yr-old mother with her computer stuff (she has an iMac) and there's so much user-hostile, broken stuff--not just on the Mac itself, but many of the internet-based services she has to use--it makes you want to take a baseball bat to the while affair.
Yeah, we wouldn't want someone who understands the most revolutionary technology in 100 years to be the technical advisor to the mayor of the largest city in the United States or anything. That would be silly.
Why do you assume she doesn't understand it? From her Wikipedia article:
"Gelobter enrolled in Brown University in 1987, eventually graduating in 2011 with a Bachelor of Science in Computer Science with a concentration in artificial intelligence and machine learning."
Long ago I was working for a programmer writing an accounting system for a client (I wrote the user docs). The machine we were replacing was an old NCR plug-board system. Programmed by wires plugged into holes on a board. One person left at the client knew how the machine worked. No one knew how the programming worked. If the wires fell out of the holes it could not be put back together again. At one time someone knew that, but the knowledge was lost. This is the system we are building again today.
reply