Post History
This has nothing to do with the source control, so the GIT support in V11 and 12 is a red herring. There is no better way of doing this, as of version 12 (April 2016). What you are doing and your ...
Answer
#3: Attribution notice added
Source: https://writers.stackexchange.com/a/22033 License name: CC BY-SA 3.0 License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision
This has nothing to do with the source control, so the GIT support in V11 and 12 is a red herring. There is no better way of doing this, as of version 12 (April 2016). What you are doing and your work around are the only two ways I know of doing what you want. In our group, we use Track Changes for the changes that we want the author to review. We don't use Track Changes for the changes that we have the authority to make without having the original writer re-review it. But this has the undesirable effect of requiring the editor to keep clicking the on/off button. Your other option would be to only allow the reviewer to annotate the doc, rather than edit the doc, but that has other painful repercussions. Finally, I will point out that in Flare 12, when you generate a PDF, Flare now has the option to print the track changes content and the comment bubbles in the PDF, so people can review the PDF file itself and see the tracked changes. I know this still doesn't directly answer the need in your question, but it is a cool new feature related to what we are talking about. The best thing to do at this point is to submit a feature request on MadCap's website giving them an example and use case. They are pretty receptive to feedback.