My favorite pandoc hack is using it to convert word docs into markdown which can then be diffed similar to source code. Works great for legal redlining.
It's the software you would have to buy, but if you have to compare files a lot I would highly recommend it. (Runs on multiple platforms, too.)
Aside from multi platform, BC has things like CSV compare and marking unimportant changes are fairly robust. I do personally prefer open source myself, but BC is certainly one of the few that I didn't mind paying for.
(I imagine it registers it as one huge change, rather than tracking a zillion individual changes, but it might be interesting to try.)
https://support.office.com/en-us/article/compare-and-merge-t...
Had this forever, here's a visual on old version of Word:
http://www.techyard.net/how-to-compare-two-word-documents-an...
For more advanced, try legal blacklining:
https://support.office.com/en-us/article/compare-document-di...
Or combine multiple sources of a similar document:
https://support.office.com/en-us/article/combine-documents-f...
That you can't concat two word files together in 2018 is ridiculous.
Of course you can!
# cat word1.doc word2.doc > word3.doc
Sounds ludicrous? So does your statement.
Setting aside the hyperbole, I believe it would be a conceptual nightmare to start defining concat of two docs. For simple cases, feel free to make copy pasta :-)
Just append the pages of document 2 to the end of document 1. Then the user can decide whether to remove the page break introduced by it. I have this in my env for doing this with PDF:
$ cat =concatpdf
#!/bin/bash
if [ "$1" = "to" ]; then
shift
gs -q -sPAPERSIZE=letter -dNOPAUSE -dBATCH -sDEVICE=pdfwrite -sOutputFile=$*
else
echo Usage: concatpdf to out.pdf in.pdf in2.pdf in3.pdf
fi
$ pandoc file1.md file2.md -o file.docx
It isn't difficult. TeX and LaTeX have been doing it since the 70s and 80s respectively.
Classic Word workflow: I make a document and send it to my boss; he makes some changes but suggests further research etc. and sends me his altered version, but I stupidly work on my own version. Making this right takes like four clicks.
This sounds like utopia. :-) Do you have a link to a page that outlines these steps?
It's good for a small fix, but not something to rely upon in your main documentation workflow.
They might not be in word, but they absolutely can be, and in fact are a superset of CLI interactions (since a GUI interaction step in e.g. Automator can invoke any shell command).
>so you're limited to the features the GUI designer thought of
And in the traditional shell pipeline (that is, not Powershell) I'm limited to working on dumb streams from one command to another.
# pandoc test.doc -o test.pdf
pandoc: Unknown reader: doc
Pandoc can convert from DOCX, but not from DOC.Is this underlining, and not redlining as defined in financial services? (redlining: differential pricing based on demographic makeup of a zip code or neighborhood)