Live data from Hacker News

Show HN: Diffs of Word documents, designed for humans

news.ycombinator.com

21–30 of 60 posts

Re: Show HN: Diffs of Word documents, designed for humans

#21
Really nice work, you guys.

Also, nice timing. I recently posted a hobby project to HN that is very similar :)

http://www.nicediff.com

https://news.ycombinator.com/item?id=5599229

The ribbon support within word itself is great. The ability to link to specific sections of the diff is also a handy feature.

Re: Show HN: Diffs of Word documents, designed for humans

#22
post #11

I NEED THIS FOR EXCEL! There's been a few discussions about Excel on HN recently and it's such a major tool in so many organizations and keeping track of changes is a nightmare. Here's a classic example: - Budgeting model for company with ~10 employees and 8 departments. Model has 30 or so sheets. Tracks all assumptions on the revenue and expense sides. Great model, built well, works excellently. - CFO goes in and ch…

Yep, this is the direction we're going in. One person I talked to diffs two Excel spreadsheets by arranging the Windows to be same size and then rapidly pressing Alt-tab! The latest versions of Excel (starting with 2010, I think) come with Track Changes: maybe that would help.

It's a blink comparator. http://en.wikipedia.org/wiki/Blink_comparator

Re: Show HN: Diffs of Word documents, designed for humans

#24
post #11

I NEED THIS FOR EXCEL! There's been a few discussions about Excel on HN recently and it's such a major tool in so many organizations and keeping track of changes is a nightmare. Here's a classic example: - Budgeting model for company with ~10 employees and 8 departments. Model has 30 or so sheets. Tracks all assumptions on the revenue and expense sides. Great model, built well, works excellently. - CFO goes in and ch…

Are you using track changes?

Re: Show HN: Diffs of Word documents, designed for humans

#26
post #11

I NEED THIS FOR EXCEL! There's been a few discussions about Excel on HN recently and it's such a major tool in so many organizations and keeping track of changes is a nightmare. Here's a classic example: - Budgeting model for company with ~10 employees and 8 departments. Model has 30 or so sheets. Tracks all assumptions on the revenue and expense sides. Great model, built well, works excellently. - CFO goes in and ch…

Are you using track changes?

Yes, it's been a while but I tried that initially. I forget why I didn't like it... maybe I'll give it another shot.

Re: Show HN: Diffs of Word documents, designed for humans

#27

Earlier quoted context omitted.

Cool. We're big fans of what you're doing at DocumentCloud. I originally got into this because I wanted a similar tool for LaTeX (my background is in physics), but after understanding how bad the existing version control tools for business documents were, we just had to start there.

Thanks, you've picked an interesting niche. Versioning text is an interesting subject, and there appear to be a bunch of tools that are teasing at the problem (many of which get discussed on the Versioned Writing google group), but none of them have really gotten things right yet. A lot of folks have been taking Github as an inspiration, and it's been cool to see what people pick and choose out of the experience.

If you use LaTeX and Git - but mandate that each sentence gets its own individual line, it works quite well for versioning, even if its not transparent to the end user

Re: Show HN: Diffs of Word documents, designed for humans

#30
This reminds me: it blows my mind how far behind the publishing industry is in terms of technology. I'm currently editing a tech book, and I get the assets from them as a Word doc and images for the figures in a zip file. I have then "track changes" in Word, save the file, and send it back. For the images, if there is an error, I have to take a new screenshot, write in the doc that there was an error, and then send back a zip file with the new image(s).

This would be SO much easier with github. I could just make my edits and issue a pull request, which would work with the image too. I could even use the commit messages to explain what the error was if need be. Github even has tools to make this process easier for non-tech people (which honestly there shouldn't be since it is a tech book!).

This will be made easier by this tool, but sadly not for me.

Post reply on HN