https://bugs.documentfoundation.org/show_bug.cgi?id=165556
Miklos Vajna <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #1 from Miklos Vajna <[email protected]> --- My understanding is that there are cases where you have to either split redlines or have overlapping redlines and Writer decided to split redlines, so we shouldn't ever have overlapping redlines, ideally. An example: 1. Alice types into the document, XY 2. Bob deletes Y This could result in a document model with 2 redlines, the insert covering "XY" and the delete covering Y, so they would overlap. But we have code in Writer to split the XY insert into 2 redlines and then the delete redline will have a second SwRedlineData that will contain the "parent" insertion. Now in Word, what you have is markup like this (DOCX): <w:ins w:id="0" w:author="M V" w:date="2025-03-04T08:54:00Z" w16du:dateUtc="2025-03-04T07:54:00Z"> <w:r> <w:t>X</w:t> </w:r> <w:del w:id="1" w:author="Miklos Vajna" w:date="2025-03-04T08:55:00Z" w16du:dateUtc="2025-03-04T07:55:00Z"> <w:r w:rsidDel="003A54BE"> <w:delText>Y</w:delText> </w:r> </w:del> </w:ins> So Word does have overlapping redlines, but they need to form proper XML nesting, so "<ins><del></ins></del>" style overlapping is not supported there, either. I would suggest that given 1) we already have code to split redlines and 2) Word can't do arbitrary overlapping to completely avoid splitting, we keep doing this the split way and ideally never have overlapping redlines in the doc model. -- You are receiving this mail because: You are the assignee for the bug.
