91–100 of 118 posts
- unzip the .docx file into xml files
- parse the xml into something organizable by line (csv? etc)
- commit this other file format
- in the GUI of your app, when someone selects a snapshot in time, go from the by line (csv? etc) format back to .docx
- open in word
- profit
(way back when we did this with excel, but ultimately gave up https://github.com/decisive-wizard/GridHub)
This is interesting, but what's wrong with "Track Changes"? (a feature Word had for at least 10+ years now). I believe for most people that is more than enough for version control purposes. For tech people that actually know what Git is and how to use it, I bet they'd want real Git integration, or they'd choose to store the document in a different (more easily managed by Git) format such as .md or .html.
This is interesting, but what's wrong with "Track Changes"? (a feature Word had for at least 10+ years now). I believe for most people that is more than enough for version control purposes. For tech people that actually know what Git is and how to use it, I bet they'd want real Git integration, or they'd choose to store the document in a different (more easily managed by Git) format such as .md or .html.
It doesn't scale. E.g. a common operation in a law firm is to send a draft of a Word document,[1] to several people for revisions and comments. You get back several redlines against a common version that some junior associate then has to integrate manually. [1] It has to be a word document for integration with tooling that does stuff like generating tables of authorities and whatnot.
This is interesting, but what's wrong with "Track Changes"? (a feature Word had for at least 10+ years now). I believe for most people that is more than enough for version control purposes. For tech people that actually know what Git is and how to use it, I bet they'd want real Git integration, or they'd choose to store the document in a different (more easily managed by Git) format such as .md or .html.
z:\presentation\2017\Skyscraper.doc
z:\presentation\2017\Skyscraper.doc.final
z:\presentation\2017\Skyscraper.doc.final.legal_edits
z:\presentation\2017\Skyscraper.doc.final2What's wrong with using a document management system instead of this?
Most DMSes utilize a "check-in/check-out" process, meaning that only one person can work the document. Others can work on "copies," but there is no way to sync their changes back into the main document stored in the DMS.
It also means that when someone checks a file out and then goes home for the weekend without checking it back in no one can update the file in the DMS without administrator support.
SVN does version control for word documents just fine.
...but people here irrationally hate svn, so you're getting unfairly downvoted.
Earlier quoted context omitted.
Word is tons more powerful than Google Docs, has add-ins, way more formatting and styling. In my mind, Google Doc is not a direct competitor to Word when it comes to professional editing and writing.
Ideally, styling should have nothing to do with editing or writing. You're talking about print (or PDF/static image) publishing, I guess?
Earlier quoted context omitted.
Word is tons more powerful than Google Docs, has add-ins, way more formatting and styling. In my mind, Google Doc is not a direct competitor to Word when it comes to professional editing and writing.
Ideally, styling should have nothing to do with editing or writing. You're talking about print (or PDF/static image) publishing, I guess?
Cool! Here's my unsolicited opinion: you preemptively answer "why wouldn't I just use git?" but I think "why is this better than track changes?" is the question prospective users are more likely to have. Comparisons to SharePoint versioning might also be helpful.
How big do you think the intersection is of people who can use git and people who want to use Microsoft Word?
Significant. Most engineering firms (web dev << the development world) have a need for proper documentation, and LibreOffice generally won't cut it either.