I do not speak for GitHub, but anonymous sources inform me that the feature only works with prose formats that have a built-in renderer. So basically, if you can preview the file, you can get a rendered diff for it.
Word-diffs are great for prose; line-based diffs are completely opaque for editing. If you've ever looked at a lot of copyediting in a line-based diff, you have no idea what actually happened. Look at some edits on Wikipedia and imagine trying to view them in a default git log... Fortunately, you can use `diff --color-words` or a tool like `wdiff` to get better diffs. (An example: http://www.gwern.net/docs/2002-radiance#diff )
15 comments
[ 2.6 ms ] story [ 41.3 ms ] threadCool feature!
Version control is a killer feature for writers, particularly those working collaboratively.
There are actually already a few projects out there that offer version control for writers. Draft and Penflip come to mind.
Draft: https://draftin.com/
Penflip: https://www.penflip.com/
This seems to confirm your suggestion :-)
I guess I'll still have to run `scm-latexdiff` manually between commits. Still it's nice to see tools evolving beyound line diffs.
1. the general idea:
> http://zenmagiclove.com/phrase-change-display.html
> https://news.ycombinator.com/item?id=5639728
*
2. an example:
> http://zenmagiclove.com/phrase-change-sample.html
> https://news.ycombinator.com/item?id=5648071
*
3. a demo with the gettysburg address:
> http://zenmagiclove.com/misc/gabal/gabal.html
> https://news.ycombinator.com/item?id=6765685
*
i have working code, if github (or anyone else) is interested.
-bowerbird
https://github.com/munificent/game-programming-patterns/comm...
[1]: http://gameprogrammingpatterns.com/