| Summary: | Marking comment as resolved doesn't get saved in DOCX format | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | gahara31 <gauraasik> |
| Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | aron.budea, fkereki, telesto |
| Priority: | medium | Keywords: | dataLoss, filter:docx |
| Version: | 6.4.4.2 release | ||
| Hardware: | All | ||
| OS: | All | ||
| See Also: |
https://bugs.documentfoundation.org/show_bug.cgi?id=119228 https://bugs.documentfoundation.org/show_bug.cgi?id=122222 |
||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
| Bug Depends on: | |||
| Bug Blocks: | 112916 | ||
| Attachments: |
A sample with a comment
Sample DOCX with a comment resolved in MSO |
||
|
Description
gahara31
2020-06-23 14:04:40 UTC
Comment hidden (obsolete)
let me rephrase it to make it more clearer. comment made by other who use ms.word, when marked as resolve in writer and saved as .docx in writer doesn't stay resolved when the file re-opened in writer. Ref: https://ask.libreoffice.org/en/question/251838 Please provide a sample DOCX with comments, which others could open in Writer, try to resolve and reopen. Thanks! Confirm using Version: 6.4.5.1 (x64) Build ID: be964ce243d03404cfeed53d0487f5d6bd49c627 CPU threads: 12; OS: Windows 10.0 Build 18363; UI render: GL; VCL: win; Locale: ru-RU (ru_RU); UI-Language: en-US Calc: CL Created attachment 162352 [details]
A sample with a comment
Created attachment 162354 [details]
Sample DOCX with a comment resolved in MSO
This would be Filesave issue, but we also have Fileopen issue:
if comment is marked Resolved in MSO, as attached, LO opens it without that mark.
Yes, that can be another issue, but let's first see what happens here.
Looks like DOCX issue only, DOC cannot handle it in MSO.
*** Bug 137053 has been marked as a duplicate of this bug. *** *** Bug 138930 has been marked as a duplicate of this bug. *** Check bug 138930 for sample files. *** This bug has been marked as a duplicate of bug 122222 *** |