Description
This document presents analysis of a change-tracked deletion example based on the current tracked-changes provisions of ODF 1.2.
It also turns up an unexpected implementation edge case that I assume applies generally to releases based on the OO.o 3.3 code base. The demonstration of the failure, which can lead to corrupted deletions that restore incorrectly when rejected, is serious enough.
I include that portion of the analysis, albeit implementation dependent, because it demonstrates the subtleties that must be understood (and should be documented in the ODF specification) in order to properly implement the deletion approach that has been appealed to since ODF 1.0.
