Even after disabling Review -> Track Changes and disabling the Review -> Show Changes check box, nothing changes in the Text editor view, which is where I prefer to work. Here's an example of a change for a single space character:
<MadCap:change MadCap:changes="2"> </MadCap:change>
I get insane amounts of this cruft in every file I edit. I never should have activated Tracking. This bug has been in Flare for almost a decade and I should have known better. So much unwanted sludge in the code for my doc files!
There MUST be a way to stop this once and for all. Thanks!
Must... stop... the change tracking...
-
ChoccieMuffin
- Senior Propellus Maximus
- Posts: 2632
- Joined: Wed Apr 14, 2010 8:01 am
- Location: Surrey, UK
Re: Must... stop... the change tracking...
I haven't checked, but is there some kind of "instruction" in the heading bit of your topic if you turn on Track Changes? If so, could you do a global search-and-replace to remove it?
Started as a newbie with Flare 6.1, now using Flare 2023.
Report bugs at http://www.madcapsoftware.com/bugs/submit.aspx.
Request features at https://www.madcapsoftware.com/feedback ... quest.aspx
Report bugs at http://www.madcapsoftware.com/bugs/submit.aspx.
Request features at https://www.madcapsoftware.com/feedback ... quest.aspx
Re: Must... stop... the change tracking...
I will check that out and respond with results.ChoccieMuffin wrote:I haven't checked, but is there some kind of "instruction" in the heading bit of your topic if you turn on Track Changes? If so, could you do a global search-and-replace to remove it?
Re: Must... stop... the change tracking...
No 'Instructions' as such - just a huge head section with information similar to the following:
<head>
<MadCap:changeData>
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="2" MadCap:timestamp="2018-11-27T16:44:09.3119174-08:00" />
<MadCap:RemoveChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="4" MadCap:timestamp="2018-11-27T16:48:12.4477618-08:00" />
<MadCap:RemoveChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="7" MadCap:timestamp="2018-11-27T16:53:55.1911017-08:00" />
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="8" MadCap:timestamp="2018-11-27T16:53:55.2170324-08:00" />
<MadCap:RemoveChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="9" MadCap:timestamp="2018-11-27T16:55:01.8169744-08:00" />
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="10" MadCap:timestamp="2018-11-27T16:55:46.9759265-08:00" />
<MadCap:RemoveChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="13" MadCap:timestamp="2018-11-27T17:00:14.0825359-08:00" />
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="14" MadCap:timestamp="2018-11-27T17:00:41.3868507-08:00" />
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="18" MadCap:timestamp="2018-11-27T17:10:28.6944137-08:00" />
<MadCap:RemoveChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="19" MadCap:timestamp="2018-11-27T17:10:46.2542890-08:00" />
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="23" MadCap:timestamp="2018-11-27T18:11:27.5794294-08:00" />
<MadCap:RemoveChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="24" MadCap:timestamp="2018-11-27T18:13:37.0248189-08:00" />
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="27" MadCap:timestamp="2018-11-28T11:33:26.6409868-08:00" />
<MadCap:RemoveChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="28" MadCap:timestamp="2018-11-28T11:34:36.5925548-08:00" />
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="29" MadCap:timestamp="2018-11-28T11:34:36.6225025-08:00" />
<MadCap:RemoveChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="30" MadCap:timestamp="2018-11-28T11:35:51.2644715-08:00" />
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="34" MadCap:timestamp="2018-11-28T11:50:59.6009833-08:00" />
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="35" MadCap:timestamp="2018-11-28T13:12:36.8379181-08:00" />
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="36" MadCap:timestamp="2018-11-28T13:14:06.6433900-08:00" />
<MadCap:RemoveChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="37" MadCap:timestamp="2018-11-28T13:14:25.8311398-08:00" />
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="38" MadCap:timestamp="2018-11-28T13:31:31.9173790-08:00" />
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="41" MadCap:timestamp="2018-11-28T13:37:21.6289058-08:00" />
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="42" MadCap:timestamp="2018-11-28T13:39:24.7819468-08:00" />
<MadCap:RemoveChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="43" MadCap:timestamp="2018-11-28T13:40:48.7339372-08:00" />
<MadCap:RemoveChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="44" MadCap:timestamp="2018-11-28T13:42:12.5766613-08:00" />
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="45" MadCap:timestamp="2018-11-28T13:42:46.0380330-08:00" />
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="46" MadCap:timestamp="2018-11-28T13:43:54.9712263-08:00" />
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="47" MadCap:timestamp="2018-11-28T13:44:56.9942133-08:00" />
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="48" MadCap:timestamp="2018-11-28T13:49:10.1916620-08:00" />
<MadCap:RemoveChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="49" MadCap:timestamp="2018-11-30T11:45:41.5143171-08:00" />
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="50" MadCap:timestamp="2018-11-30T11:45:41.5691689-08:00" />
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="51" MadCap:timestamp="2018-11-30T11:49:29.4640978-08:00" />
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="52" MadCap:timestamp="2018-11-30T12:13:56.4481487-08:00" />
</MadCap:changeData>
And massive numbers of insertions into the body such as the following:
<p MadCap:conditions="General.Exclude">Because <MadCap:change MadCap:changes="50">the device</MadCap:change><MadCap:change MadCap:changes="49">it</MadCap:change> remains in the device list<MadCap:change MadCap:changes="43"> and is reachable, </MadCap:change><MadCap:change MadCap:changes="52"> until a field technician restores it to operation, </MadCap:change>you can <MadCap:change MadCap:changes="51">quickly </MadCap:change><MadCap:change MadCap:changes="49">return to the device and </MadCap:change>re-establish its operation<MadCap:change MadCap:changes="18"> and management </MadCap:change><MadCap:change MadCap:changes="19"> at any time</MadCap:change> (<b MadCap:changes="14">Wakeup</b><MadCap:change MadCap:changes="13">Unrevoke</MadCap:change>)<MadCap:change MadCap:changes="29"> when the conditions mandating the Hibernation or Winterizing conclude</MadCap:change><MadCap:change MadCap:changes="28"> after issue resolution</MadCap:change>.<MadCap:change MadCap:changes="51"> By the end of Wakeup, the device will return to Enrolled status.</MadCap:change></p>
This is insane. I'm not sure that even using wildcards would help with that.
<head>
<MadCap:changeData>
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="2" MadCap:timestamp="2018-11-27T16:44:09.3119174-08:00" />
<MadCap:RemoveChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="4" MadCap:timestamp="2018-11-27T16:48:12.4477618-08:00" />
<MadCap:RemoveChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="7" MadCap:timestamp="2018-11-27T16:53:55.1911017-08:00" />
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="8" MadCap:timestamp="2018-11-27T16:53:55.2170324-08:00" />
<MadCap:RemoveChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="9" MadCap:timestamp="2018-11-27T16:55:01.8169744-08:00" />
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="10" MadCap:timestamp="2018-11-27T16:55:46.9759265-08:00" />
<MadCap:RemoveChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="13" MadCap:timestamp="2018-11-27T17:00:14.0825359-08:00" />
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="14" MadCap:timestamp="2018-11-27T17:00:41.3868507-08:00" />
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="18" MadCap:timestamp="2018-11-27T17:10:28.6944137-08:00" />
<MadCap:RemoveChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="19" MadCap:timestamp="2018-11-27T17:10:46.2542890-08:00" />
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="23" MadCap:timestamp="2018-11-27T18:11:27.5794294-08:00" />
<MadCap:RemoveChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="24" MadCap:timestamp="2018-11-27T18:13:37.0248189-08:00" />
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="27" MadCap:timestamp="2018-11-28T11:33:26.6409868-08:00" />
<MadCap:RemoveChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="28" MadCap:timestamp="2018-11-28T11:34:36.5925548-08:00" />
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="29" MadCap:timestamp="2018-11-28T11:34:36.6225025-08:00" />
<MadCap:RemoveChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="30" MadCap:timestamp="2018-11-28T11:35:51.2644715-08:00" />
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="34" MadCap:timestamp="2018-11-28T11:50:59.6009833-08:00" />
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="35" MadCap:timestamp="2018-11-28T13:12:36.8379181-08:00" />
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="36" MadCap:timestamp="2018-11-28T13:14:06.6433900-08:00" />
<MadCap:RemoveChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="37" MadCap:timestamp="2018-11-28T13:14:25.8311398-08:00" />
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="38" MadCap:timestamp="2018-11-28T13:31:31.9173790-08:00" />
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="41" MadCap:timestamp="2018-11-28T13:37:21.6289058-08:00" />
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="42" MadCap:timestamp="2018-11-28T13:39:24.7819468-08:00" />
<MadCap:RemoveChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="43" MadCap:timestamp="2018-11-28T13:40:48.7339372-08:00" />
<MadCap:RemoveChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="44" MadCap:timestamp="2018-11-28T13:42:12.5766613-08:00" />
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="45" MadCap:timestamp="2018-11-28T13:42:46.0380330-08:00" />
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="46" MadCap:timestamp="2018-11-28T13:43:54.9712263-08:00" />
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="47" MadCap:timestamp="2018-11-28T13:44:56.9942133-08:00" />
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="48" MadCap:timestamp="2018-11-28T13:49:10.1916620-08:00" />
<MadCap:RemoveChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="49" MadCap:timestamp="2018-11-30T11:45:41.5143171-08:00" />
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="50" MadCap:timestamp="2018-11-30T11:45:41.5691689-08:00" />
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="51" MadCap:timestamp="2018-11-30T11:49:29.4640978-08:00" />
<MadCap:AddChange MadCap:userName="RichardG" MadCap:initials="RI" MadCap:id="52" MadCap:timestamp="2018-11-30T12:13:56.4481487-08:00" />
</MadCap:changeData>
And massive numbers of insertions into the body such as the following:
<p MadCap:conditions="General.Exclude">Because <MadCap:change MadCap:changes="50">the device</MadCap:change><MadCap:change MadCap:changes="49">it</MadCap:change> remains in the device list<MadCap:change MadCap:changes="43"> and is reachable, </MadCap:change><MadCap:change MadCap:changes="52"> until a field technician restores it to operation, </MadCap:change>you can <MadCap:change MadCap:changes="51">quickly </MadCap:change><MadCap:change MadCap:changes="49">return to the device and </MadCap:change>re-establish its operation<MadCap:change MadCap:changes="18"> and management </MadCap:change><MadCap:change MadCap:changes="19"> at any time</MadCap:change> (<b MadCap:changes="14">Wakeup</b><MadCap:change MadCap:changes="13">Unrevoke</MadCap:change>)<MadCap:change MadCap:changes="29"> when the conditions mandating the Hibernation or Winterizing conclude</MadCap:change><MadCap:change MadCap:changes="28"> after issue resolution</MadCap:change>.<MadCap:change MadCap:changes="51"> By the end of Wakeup, the device will return to Enrolled status.</MadCap:change></p>
This is insane. I'm not sure that even using wildcards would help with that.
-
ChoccieMuffin
- Senior Propellus Maximus
- Posts: 2632
- Joined: Wed Apr 14, 2010 8:01 am
- Location: Surrey, UK
Re: Must... stop... the change tracking...
Lightbulb moment.
In the XML Editor you need to ACCEPT or REJECT the changes, then turn off Track Changes. By accepting or rejecting a change you remove the crud in your text editor for that change. Work through the topic and accept or reject each change then save. I bet all the crud in the Text Editor view will have miraculously disappeared!
The purpose of the track changes feature is to show your changes in the XML Editor, so if you predominantly work in the Text Editor you're just making a rod for your own back - a more suitable way to track changes in that case might to use a comparison tool to review changes between one version or another.
Hope that helps, and please report back.
In the XML Editor you need to ACCEPT or REJECT the changes, then turn off Track Changes. By accepting or rejecting a change you remove the crud in your text editor for that change. Work through the topic and accept or reject each change then save. I bet all the crud in the Text Editor view will have miraculously disappeared!
The purpose of the track changes feature is to show your changes in the XML Editor, so if you predominantly work in the Text Editor you're just making a rod for your own back - a more suitable way to track changes in that case might to use a comparison tool to review changes between one version or another.
Hope that helps, and please report back.
Started as a newbie with Flare 6.1, now using Flare 2023.
Report bugs at http://www.madcapsoftware.com/bugs/submit.aspx.
Request features at https://www.madcapsoftware.com/feedback ... quest.aspx
Report bugs at http://www.madcapsoftware.com/bugs/submit.aspx.
Request features at https://www.madcapsoftware.com/feedback ... quest.aspx
Re: Must... stop... the change tracking...
OMG. So simple. You can also use Accept All Changes in each project file, in the XML Editor. BAM! All the cruft is gone.ChoccieMuffin wrote:Lightbulb moment.
In the XML Editor you need to ACCEPT or REJECT the changes, then turn off Track Changes. By accepting or rejecting a change you remove the crud in your text editor for that change. Work through the topic and accept or reject each change then save. I bet all the crud in the Text Editor view will have miraculously disappeared!
The purpose of the track changes feature is to show your changes in the XML Editor, so if you predominantly work in the Text Editor you're just making a rod for your own back - a more suitable way to track changes in that case might to use a comparison tool to review changes between one version or another.
Hope that helps, and please report back.
That single file I used as an example got cut down from 16K to 7K.
Brilliant. THANKS ChoccieMuffin.
-
ChoccieMuffin
- Senior Propellus Maximus
- Posts: 2632
- Joined: Wed Apr 14, 2010 8:01 am
- Location: Surrey, UK
Re: Must... stop... the change tracking...
Delighted to help.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Started as a newbie with Flare 6.1, now using Flare 2023.
Report bugs at http://www.madcapsoftware.com/bugs/submit.aspx.
Request features at https://www.madcapsoftware.com/feedback ... quest.aspx
Report bugs at http://www.madcapsoftware.com/bugs/submit.aspx.
Request features at https://www.madcapsoftware.com/feedback ... quest.aspx
Re: Must... stop... the change tracking...
What if my document changes are not approved yet, and therefore cannot accept the changes because I still need the redlines. Is there a way to show the files in final form, but keep the track changes? Reviewers want to see the files in "draft" final form, instead of reading through all of the markup. Is there a way to do this in Flare?
-
ChoccieMuffin
- Senior Propellus Maximus
- Posts: 2632
- Joined: Wed Apr 14, 2010 8:01 am
- Location: Surrey, UK
Re: Must... stop... the change tracking...
I suspect this help topic gives you your answer: http://help.madcapsoftware.com/flare201 ... hanges.htmmmlsadkin wrote:What if my document changes are not approved yet, and therefore cannot accept the changes because I still need the redlines. Is there a way to show the files in final form, but keep the track changes? Reviewers want to see the files in "draft" final form, instead of reading through all of the markup. Is there a way to do this in Flare?
Although this tells you how to PRESERVE tracked changes, I would imagine doing the opposite will allow you to ignore the tracking. (Or would it instead just produce a document without any of the changes you've made? Hmm... think you'll need to test it...)
Started as a newbie with Flare 6.1, now using Flare 2023.
Report bugs at http://www.madcapsoftware.com/bugs/submit.aspx.
Request features at https://www.madcapsoftware.com/feedback ... quest.aspx
Report bugs at http://www.madcapsoftware.com/bugs/submit.aspx.
Request features at https://www.madcapsoftware.com/feedback ... quest.aspx
Re: Must... stop... the change tracking...
Unfortunately, if you clear the Preserve tracked changes check box when you build a PDF, the changes don't show up in the PDF, and the content basically reverts back to before changes.
-
Nita Beck
- Senior Propellus Maximus
- Posts: 3669
- Joined: Thu Feb 02, 2006 9:57 am
- Location: Pittsford, NY
Re: Must... stop... the change tracking...
How about outputting to Word with preserved track changes and then, in Word and prior to giving your reviewers the doc, you accept the changes. That way, your reviewers will at least get to read through the final content (although perhaps not exactly formatted as it would be online).
Just thinking out loud... And if I’ve gotten myself all confused, sorry, it’s been a long week.
Just thinking out loud... And if I’ve gotten myself all confused, sorry, it’s been a long week.
Nita
RETIRED, but still fond of all the Flare friends I've made. See you around now and then!
RETIRED, but still fond of all the Flare friends I've made. See you around now and then!