This is an automated email from the ASF dual-hosted git repository. jimjag pushed a commit to branch odf-devel in repository https://gitbox.apache.org/repos/asf/openoffice.git
commit 218fb79f6b3c7642bd1cae187126ac3b5446821b Author: Jim Jagielski <[email protected]> AuthorDate: Fri Oct 23 13:40:03 2026 -0400 xmloff: don't write a redline successor --- main/xmloff/source/text/XMLRedlineExport.cxx | 24 ------------------------ 1 file changed, 24 deletions(-) diff --git a/main/xmloff/source/text/XMLRedlineExport.cxx b/main/xmloff/source/text/XMLRedlineExport.cxx index 180c727555..fc527490e9 100644 --- a/main/xmloff/source/text/XMLRedlineExport.cxx +++ b/main/xmloff/source/text/XMLRedlineExport.cxx @@ -405,30 +405,6 @@ void XMLRedlineExport::ExportChangedRegion( // else: no text interface -> content is inline and will // be exported there } - - // changed change? Hierarchical changes can onl be two levels - // deep. Here we check for the second level. - aAny = rPropSet->getPropertyValue(sRedlineSuccessorData); - Sequence<PropertyValue> aSuccessorData; - aAny >>= aSuccessorData; - - // if we actually got a hierarchical change, make element and - // process change info - // ODF 1.2 allows one change per changed region, so the successor is extended-mode only - if (aSuccessorData.getLength() > 0 && - rExport.getDefaultVersion() > SvtSaveOptions::ODFVER_012) - { - // The only change that can be "undone" is an insertion - - // after all, you can't re-insert an deletion, but you can - // delete an insertion. This assumption is asserted in - // ExportChangeInfo(Sequence<PropertyValue>&). - SvXMLElementExport aSecondChangeElem( - rExport, XML_NAMESPACE_TEXT, XML_INSERTION, - sal_True, sal_True); - - ExportChangeInfo(aSuccessorData); - } - // else: no hierarchical change }
