Best practices with Oygen "Track Changes" and Git
Posted: Sat Feb 27, 2016 1:18 am
We've run into some issues where "Track Changes" seems to change XML files in wide-sweeping ways, such as completely rewrapping the whole file. These types of changes make it difficult to apply this type of commit to multiple Git branches. Is there any way we can limit the 'damage' that turning on Track Changes does on a per-line basis? Any other advice about Oxygen configuration, best practices, or workflows using Track Changes with a line-based VCS like Git?
Re: Best practices with Oygen "Track Changes" and Git
Posted: Mon Feb 29, 2016 11:23 am
Not sure how to advice you here. Change tracking is kept by Oxygen as processing instructions, meaning that indeed it affects the lines of content in the XML.
Maybe you could first create a GIT branch on which the review is done, then after all the changes, they would all get accepted on that branch and then commit on the main branch the content without any Oxygen change tracking. So the main GIT branch would never contain Oxygen change tracking instruction.