Description: Let's say I'm in CET timezone, 15:00 local time. I create new Writer document and save it as .docx (2007-365). Then I open it as archive and go to: docProps > core.xml there I can see: <dcterms:created xsi:type="dcterms:W3CDTF">2020-07-06T15:00:00Z</dcterms:created> but this is wrong, since the date has Z on the end it means that this is UTC timestamp. it should be like this: <dcterms:created xsi:type="dcterms:W3CDTF">2020-07-06T13:00:00Z</dcterms:created> or just timezone naive: <dcterms:created xsi:type="dcterms:W3CDTF">2020-07-06T15:00:00</dcterms:created> because of this some libraries, as python-docx, may have issues with timezones. same goes for the review comments: LibreOffice saves it as local time, but adds UTC 'Z' to the timestamp. Microsoft Office works differently and just put timestamps in the naive way inside (for comments) or in proper timezone (for creation date) Steps to Reproduce: 1.Create new Writer doc 2.Export to docx 3.Open it as archive 4.Check creation timestamp Actual Results: <dcterms:created xsi:type="dcterms:W3CDTF">2020-07-06T15:00:00Z</dcterms:created> Expected Results: <dcterms:created xsi:type="dcterms:W3CDTF">2020-07-06T15:00:00</dcterms:created> Reproducible: Always User Profile Reset: Yes Additional Info: Link to the forum: https://ask.libreoffice.org/en/question/253816/timezone-of-creation-date-for-docx-file/
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Created attachment 163396 [details] reproduce of the bug In the attachment: my current local data time (Europe/Amsterdam) is 09:34 in the document I can see: <dcterms:created xsi:type="dcterms:W3CDTF">2020-07-22T09:34:54Z</dcterms:created> 2020-07-22T09:34:54Z - is the UTC time format, not the local one. It should be: <dcterms:created xsi:type="dcterms:W3CDTF">2020-07-22T07:34:54Z</dcterms:created> or <dcterms:created xsi:type="dcterms:W3CDTF">2020-07-22T09:34:54</dcterms:created>
[Automated Action] NeedInfo-To-Unconfirmed
Reproduced Arch Linux 64-bit Version: 7.2.0.0.alpha0+ / LibreOffice Community Build ID: 13aaeb5d148c1ea5163eecaa176fac4a67689277 CPU threads: 8; OS: Linux 5.12; UI render: default; VCL: gtk3 Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 7 May 2021
I push a possible fix to Gerrit: https://gerrit.libreoffice.org/c/core/+/120561 But some unit test fails, could anyone check how can fix it?
Hello virusmater, Thank you for reporting the bug. Unfortunately I don't find how check creation timestamp. In LibreOffice : 22/07/2020, 09:34:54 In PowerShell : -a--- 02/03/2024 10:25 4178 Bug_134589.docx In the Download folder : samedi 2 mars 2024, 10:35:48 Please provide a clearer set of step-by-step instructions on how to reproduce this step. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the steps are provided Thanks
Dear virusmater, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear virusmater, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp