Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Post History

66%
+2 −0
Q&A Text Editors. Suggesting & Tracking Changes to Plain-Text Documents

This is a good question. Unfortunately, outside of the programming realm, there's no system for tracking changes at the character level that I'm aware of. (If there is one, I'd love to know about i...

posted 12y ago by Neil‭  ·  edited 3y ago by Canina‭

Answer
#4: Post edited by user avatar Canina‭ · 2021-05-20T18:57:16Z (over 3 years ago)
  • This is a good question. Unfortunately, outside of the programming realm, there's no system for tracking changes at the character level that I'm aware of. (If there is one, I'd love to know about it!) I suspect there are many, many such systems that have been cobbled together by individuals, however.
  • This comes up often when blogging: Do we use Word files with their awesome change tracking features and then deal with all the garbage they produce before posting (possibly introducing errors)? Or do we work in plain text from the start, cobbling together some sort of change system like the one Michael suggests?
  • If you absolutely need something like this, I recommend using marks that are catch the eye. [[[triple brackets]]] or \*\*\*lots of asterisks\*\*\* or ###other such signs###. (If you're working on source code or HTML, this could cause problems later. And, as you can see, sometimes **_lots of asterisks_** render as bold-italic text, indicating yet another problem.)
  • Rather than embedding changes in the text itself, is it possible you could simply use versioning and the name of the person? For example, SampleFile\_EditorNF\_v1.0.1.txt may have meaning if you and your colleagues have agreed on a system. You could then use the compare revisions of a robust editor (such as BBEdit) to compare versions and see the changes.
  • Another option is to use commenting to describe the changes.
  • This is a good question. Unfortunately, outside of the programming realm, there's no system for tracking changes at the character level that I'm aware of. (If there is one, I'd love to know about it!) I suspect there are many, many such systems that have been cobbled together by individuals, however.
  • This comes up often when blogging: Do we use Word files with their awesome change tracking features and then deal with all the garbage they produce before posting (possibly introducing errors)? Or do we work in plain text from the start, cobbling together some sort of change system like the one suggested in a previous answer?
  • If you absolutely need something like this, I recommend using marks that are catch the eye. [[[triple brackets]]] or \*\*\*lots of asterisks\*\*\* or ###other such signs###. (If you're working on source code or HTML, this could cause problems later. And, as you can see, sometimes **_lots of asterisks_** render as bold-italic text, indicating yet another problem.)
  • Rather than embedding changes in the text itself, is it possible you could simply use versioning and the name of the person? For example, SampleFile\_EditorNF\_v1.0.1.txt may have meaning if you and your colleagues have agreed on a system. You could then use the compare revisions of a robust editor (such as BBEdit) to compare versions and see the changes.
  • Another option is to use commenting to describe the changes.
#3: Attribution notice added by user avatar System‭ · 2019-12-08T02:37:54Z (almost 5 years ago)
Source: https://writers.stackexchange.com/a/6866
License name: CC BY-SA 3.0
License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision by (deleted user) · 2019-12-08T02:37:54Z (almost 5 years ago)
This is a good question. Unfortunately, outside of the programming realm, there's no system for tracking changes at the character level that I'm aware of. (If there is one, I'd love to know about it!) I suspect there are many, many such systems that have been cobbled together by individuals, however.

This comes up often when blogging: Do we use Word files with their awesome change tracking features and then deal with all the garbage they produce before posting (possibly introducing errors)? Or do we work in plain text from the start, cobbling together some sort of change system like the one Michael suggests?

If you absolutely need something like this, I recommend using marks that are catch the eye. [[[triple brackets]]] or \*\*\*lots of asterisks\*\*\* or ###other such signs###. (If you're working on source code or HTML, this could cause problems later. And, as you can see, sometimes **_lots of asterisks_** render as bold-italic text, indicating yet another problem.)

Rather than embedding changes in the text itself, is it possible you could simply use versioning and the name of the person? For example, SampleFile\_EditorNF\_v1.0.1.txt may have meaning if you and your colleagues have agreed on a system. You could then use the compare revisions of a robust editor (such as BBEdit) to compare versions and see the changes.

Another option is to use commenting to describe the changes.

#1: Imported from external source by user avatar System‭ · 2012-12-21T22:17:42Z (almost 12 years ago)
Original score: 1