How do those work with the rest of the git machinery? Does git add -p work? How are merge conflicts handled? What about git blame?
It seems to me that that everything about git is based on text files that are changed by adding and removing lines, but if there is a way to replace that behavior to handle non-textual file formats, I'd be very interesting in learning about it.
Unfortunately, this particular review tool was an internal utility at my previous employer. The only thing it could do was highlight changes in word documents. You could compare patch sets. That's all. And it was a review tool. Git itself still treated docx files more or less like binaries. The advantage was we could use word documents instead of markdown files, usually people would embed visio diagrams inside design docs etc.
It seems to me that that everything about git is based on text files that are changed by adding and removing lines, but if there is a way to replace that behavior to handle non-textual file formats, I'd be very interesting in learning about it.