Description: When exporting an MS Word document from SharePoint and afterwards embedding a custom date property inside said document, Libre Office is unable to display this property correctly. In the attachments, I have provided two documents, one of which was initially saved in MS Word. This document will be displayed correctly in MS Word but when opening it in Libre Office the date property is set to “ 30.12.1899 00:00:00” instead of “01.02.2024 15:00:00”. The suspected problem is that Libre Office is unable to parse the underlying xpath which links to the value of the date property. This is likely the case because when opening the document in LibreOffice, setting the property to a new value and afterwards saving it, the xpath is different from the original one. As shown below the original xpaht is different from the updated one. The only difference between them is that saving the initial document decodes the underscore into x005F which represents said character. So the bug results from not being able to decode the xpath correctly and updating it to a parsable format. As additional information, I have provided the two documents as attachments. The first one named “initialWord.docx” is the initial document exported from SharePoint and the second one is the updated one saved in Libre Office named “updatedLibreOffice.docx”. Steps to Reproduce: 1. Open the document from attachments in MS Word 2. Insert document property 2. Save document 4. Open document in Libre Office Actual Results: 30.12.1899 00:00:00 probably caused by: w:xpath="/ns0:properties[1]/documentManagement[1]/ns3:q_Freigabe_x005F_x002d_Datum[1]" Expected Results: 01.02.2024 15:00:00 caused by the correct xpath: w:xpath="/ns0:properties[1]/documentManagement[1]/ns3:q_Freigabe_x002d_Datum[1]" Reproducible: Always User Profile Reset: No Additional Info: -
Created attachment 192875 [details] original Document, use for further testing
Created attachment 192876 [details] updated document in Libre Office
Reproducible Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 6a064b1967e06e40be40817deff99d00c1a8554f CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded The field it's converted to a 'Content Control'
Dear fmanchen, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug