OS = Window7 - Home Premium SP1 (32 and 64 bits); MS-Office 2010;
LibreOffice 184.108.40.206 (Build ID: 1c1366bba2ba2b554cd2ca4d87c06da81c05d24).
As I’m updating various documents frequently, saving with a version number in the document name isn’t enough to recognize differences in printed pages. Therefor I use the SAVEDATE field of MS-Word in the header. When now migrating to LO the doc name and date are reproduced, but the time stamp changes into “H:02”.
Correcting the timestamp in LO and saving the document in the ODT-environment works perfect, including correct information in the header when printing.
But….. as I must share most of the documents with other people, I need to save some documents after updating in DOC or DOCX format.
= Saving as MS-2003-DOC gives in my header an old doc name and not updated date and time.
= Saving as MS-2007/2010-DOCX shows in the header old doc name and wrong time.
= Saving as Office Open XML-DOCX shows old doc name and date and time as zero.
Is there a fix planned to make sure the actual document name, date and time of the last changes could be saved just in the old MS-DOC format?
Created attachment 94072 [details]
An overview given of a number of tests in migration between various doc extensions
I confirm the "HH:02" in header.
Win 7 64-bit, Version: 220.127.116.11.alpha1+
Build ID: 14a2cfc27f86112469f2a2252bdc154ad8d3219f
TinderBox: Win-x86@42, Branch:master, Time: 2014-10-28_04:51:26
Well the HH:02 is in the header in Word 2010, so I don't get the point of this report.
Please provide a document, where the timestamp is working in MS Word!
Dear Bug Submitter,
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 INVALID
due to lack of needed information.
For more information about our NEEDINFO policy please read the
wiki located here:
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!
Dear Bug Submitter,
Please read this message in its entirety before proceeding.
Your bug report is being closed as INVALID 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
-- The LibreOffice QA Team
This INVALID Message was generated on: 2015-05-06