Live data from Hacker News

Ask HN: “Git” for Microsoft Office?

news.ycombinator.com

1–10 of 149 posts

Ask HN: “Git” for Microsoft Office?

#1
I’ve recently changed job and now I am basically swamped in MSOffice documents. This makes collaboration very hard: people are fearful you’ll touch their precious files, there are manual procedures to produce “gold” documents, fixing a typo is an ordeal, and if the same slide is present in 15 Powerpoint decks any edit will require tons of mindless and error-prone copypasting... it made me realize how good developers have it with git, github, and the likes.

Is there anything out there, capable of working with MSOffice stuff in a granular and collaborative way? I can’t believe non-geeks have lived like this for 30 years.

Re: Ask HN: “Git” for Microsoft Office?

#5
O365 has had live editing for a while now[1], it's not even that hard to use.

You can have that Golden Version and everyone can suggest changes and edits, then the document owner can accept or decline the edits.

[1]: https://support.office.com/en-us/article/Collaborate-on-Word...

Re: Ask HN: “Git” for Microsoft Office?

#7
Technically, tracked changes and SharePoint. But in practice, you’d rather send the changes to the project owner via carrier pigeon.

I’ve looked into what it would take to make a git style system for docx (since it’s just zipped XML, right :D), and the file format was a nightmare whenever an edit was made. Someone smart should take a look at it, as there would be a massive market for a DVCS for Office files. Imagine a world where every bill in Congress was committed to a central repo so the whole world could see the changes, or where someone in your team wants to play with the formatting on a shared requirements document without breaking the page you’re writing on. It would be a boon for productivity.

Re: Ask HN: “Git” for Microsoft Office?

#8
Using Office365 versions with Track Changes turned on is probably the most viable option with normal people.

Technically, you could use git, and it works decently with the xml-based Office file types, but it's a hard job to get people used to the workflow, and things like merge conflicts are going to be even more of a headache.

Post reply on HN