Related to: FILEOPEN
In MS Office 2007 and 2010, total editing time is saved in minutes. However, LibreOffice believes it to be in seconds. This leads to grossly incorrect conversions for the Total Editing Time property.
Fixing this is very important for long-term Office users moving to LibreOffice and .odt. This is a simple calculation error. It should be a simple fix for the next version. I've shown my calculations for a suggested correction.
When I import a .docx file with 36,523 minutes of editing, LibreOffice claims that there is only 10:08:43 of editing time.
Running Libre Office 3.4.0, MS Office 2010 and Windows 7 64-Bit Pro
Import any .docx file and compare total editing time under properties
LibreOffice does this [ TOTALMINUTES / 60 /60 = H:M:S ]
Example (Incorrect Calculation - Current Method)
36523/60/60 = 10.14527 Hours -> .14257 * 60 = 8.71667 M -> .7167 * 60 = 43 S
Total 10 Hours 08 Minutes 43 Seconds
It should do this [TOTALMINUES / 60 / 24 = D:H:M:S ]
Example (Correct Calculation - Future Method)
36523/60/24 = 25.3632 Days -> .3632 *24 = 8.716 Hours -> .716 * 60 = 43 Minutes
Total 25 Days 8 Hours 43 Minutes
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Thanks for bugreport
Please, attach sample docx file and write, how long it edited (true value)
So, developers can verify how this works
Dear bug submitter!
Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.
To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement
Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.