https://bugs.documentfoundation.org/show_bug.cgi?id=104797
Bug ID: 104797
Summary: FILEOPEN [DOCX filter]: track changes move of string
not parsed
Product: LibreOffice
Version: 5.2.3.3 release
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: filters and storage
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: documentfoundat...@rubenvandeven.com
Description:
The track changes feature seems not to pick up on the moveFrom and moveTo
change in a docx document. More problamatically: it shows the text at both the
original position, as well as the new position. Without marking either as a
change.
This is apparently a feature introduced in Word 2007: "In Word 2007 there are
almost no changes to the "track changes" feature with the exception of move
tracking: Word displays moved sentences/paragraphs differently from
deleted/pasted ones." - https://wiki.documentfoundation.org/Track_changes
Unfortunately I don't have Word to reproduce it, so I'd suggest it can be two
things:
- This is not implemented in the filter
- In my case it was not picked up, because the moveTo position contains other
tracked changes (please see the additional information)
Steps to Reproduce:
1. Open a docx document that has tracked changes of a _movement_ of a text
string
2. See that the string is displayed at both the original position, as well as
the new position.
Actual Results:
Moved sentence. Text after first sentence. Moved sentence.
Expected Results:
Text after first sentence. Moved sentence.
Reproducible: Always
User Profile Reset: No
Additional Info:
In the docx file I found (document.xml):
(seemingly) relevant bits in the docx file (document.xml):
<w:moveFromRangeStart w:id="408" w:author="xxx" w:date="2016-12-08T15:50:00Z"
w:name="move342831535"/><w:moveFrom w:id="409" w:author="xxx"
w:date="2016-12-08T15:50:00Z"><w:r w:rsidRPr="009D78DE"
w:rsidDel="00347853"><w:rPr><w:sz w:val="26"/><w:lang
w:val="en-US"/></w:rPr><w:t xml:space="preserve">It is unclear what is being
measured. </w:t></w:r></w:moveFrom><w:moveFromRangeEnd w:id="408"/>
and later
<w:moveToRangeStart w:id="413" w:author="xxx" w:date="2016-12-08T15:50:00Z"
w:name="move342831535"/><w:moveTo w:id="414" w:author="xxx"
w:date="2016-12-08T15:50:00Z"><w:del w:id="415" w:author="xxx"
w:date="2016-12-08T15:50:00Z"><w:r w:rsidR="00347853" w:rsidRPr="009D78DE"
w:rsidDel="00347853"><w:rPr><w:sz w:val="26"/><w:lang
w:val="en-US"/></w:rPr><w:delText>It is unclear
w</w:delText></w:r></w:del></w:moveTo><w:ins w:id="416" w:author="xxx"
w:date="2016-12-08T15:50:00Z"><w:r w:rsidR="00347853"><w:rPr><w:sz
w:val="26"/><w:lang w:val="en-US"/></w:rPr><w:t>W</w:t></w:r></w:ins><w:moveTo
w:id="417" w:author="xxx" w:date="2016-12-08T15:50:00Z"><w:r w:rsidR="00347853"
w:rsidRPr="009D78DE"><w:rPr><w:sz w:val="26"/><w:lang
w:val="en-US"/></w:rPr><w:t>hat is being measured</w:t></w:r></w:moveTo><w:ins
w:id="418" w:author="xxx" w:date="2016-12-08T15:50:00Z"><w:r
w:rsidR="00347853"><w:rPr><w:sz w:val="26"/><w:lang w:val="en-US"/></w:rPr><w:t
xml:space="preserve"> thus remains unclear</w:t></w:r></w:ins><w:moveTo
w:id="419" w:author="xxx" w:date="2016-12-08T15:50:00Z"><w:r w:rsidR="00347853"
w:rsidRPr="009D78DE"><w:rPr><w:sz w:val="26"/><w:lang
w:val="en-US"/></w:rPr><w:t>.</w:t></w:r><w:del w:id="420" w:author="xxx"
w:date="2016-12-08T15:50:00Z"><w:r w:rsidR="00347853" w:rsidRPr="009D78DE"
w:rsidDel="00347853"><w:rPr><w:sz w:val="26"/><w:lang
w:val="en-US"/></w:rPr><w:delText xml:space="preserve">
</w:delText></w:r></w:del></w:moveTo><w:moveToRangeEnd w:id="413"/>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
Firefox/45.0
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
