Help > Authoring > Change Tracking > Limitations of Change Tracking
  
Limitations of Change Tracking
Some types of changes cannot be tracked, accepted, or rejected.
In Change Tracking, sometimes a change cannot be accepted or rejected because it is part of another change. The Change Record will warn you if a particular change cannot be accepted or rejected because it is part of another set of changes. This happens most often when changes from different users overlap or are surrounded.
Arbortext Editor will alert you if you attempt to make changes that can't be tracked. You can control these alerts using Change Tracking Warnings in ToolsPreferencesWarnings.
Changes that are not tracked, but an alert is provided:
Inserting or deleting of marked sections.
Editing an existing equation. Insertions and deletions are tracked.
Inserting an accent on a character.
Changing case.
Performing most table operations:
Inserting or deleting rows or columns.
Changing row height or column width.
Spanning or unspanning cells.
Inserting, deleting, or splitting grids.
Modifying table, cell, border or cell font.
Modifying table element attributes.
* 
Changes made to the contents of cells or directly to table markup will be tracked.
Changes that are not tracked, and no alert is provided:
Operations that cannot be undone in Arbortext Editor:
Declaring, changing, or undeclaring an entity, marked section, or notation.
Defining, changing, or undefining a user declared tag.
All changes made to CDATA content or elements that have CDATA content.
Undo and redo operations performed while editing.
Changing the top-level element (for example, book). This applies to the top-level element in an entity, as well as the top-level element in a document.
Operations that are not compatible with change tracking:
Typing in overstrike mode. Overstrike mode is automatically disabled when change tracking is activated.
Character substitution or character cycling.
Limitations in displaying or printing tracked changes:
A document with change tracking revisions from a release prior to 5.4 will display tracked changes in green underline and red strikethrough. User colors will not be automatically assigned.
To assign changes by user color, you will need to manually assign a user color for each author in Advanced Change Tracking Options. . You will also need to check the box to Display with user specific colors.
A deletion of a graphic or an equation will display with an X overstrike in print or published output except for HTML, which doesn’t have that capability.
If you are publishing from a DITA map, the Print Preview, Print, and File > Publish dialog boxes will always display the Change Tracking selector, and it will be initially set to Changes Applied. When publishing from a DITA Map, the Change Tracking view that's selected applies only to the topics referenced from the DITA maps. The DITA map itself, and any other referenced maps, will always be published with Changes Applied, regardless of the Change Tracking view selected (even if the maps have change tracking markup).