Summary: | FILEOPEN xslx: document property TotalTime misinterpreted as seconds instead of minutes | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Andreas J Guelzow <aguelzow> |
Component: | Spreadsheet | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | NEW --- | QA Contact: | |
Severity: | trivial | ||
Priority: | medium | CC: | LibreOffice |
Version: | 3.3.2 release | ||
Hardware: | Other | ||
OS: | Windows (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
sample file
Screenshots, See Comment 2 |
Description
Andreas J Guelzow
2011-06-26 11:13:06 UTC
Created attachment 48446 [details]
sample file
After lots of irrelevant tests I found: A1) Sample document can be used with LibO, Gnumeric, MS-XLS-Viewer without problems A2) /docProps/app.xml of test document contains <TotalTime>1</TotalTime> (what ever that might mean. B1) "LibreOffice 3.4.2 - WIN7 Home Premium (64bit) German UI [OOO340m1 (Build:203)]" shows document properties incomplete and damaged, especially time information is unusable (see screenshots!) B2) Gnumeric only shows very few document properties information, irrelevant for the tests B3) looks good with Master "LibO-dev 3.4.5 – WIN7 Home Premium (64bit) English UI [(Build ID:d337f79-a24c961-2865670-9752b71-7f8fd43 2fdd60d-fd28b6a-fd7bf20-aa369cb-28da3fb 6a9633a-931d089-ecd263f-c9b55e9-b31b807 82ff335-599f7e9-bc6a545-1926fdf)]" (see screenshots) But indeed "Total Editing Time" is shown as seconds, not minutes. ECMA-376 is available from <http://www.ecma-international.org/publications/standards/Ecma-376.htm> In Part 1 "ECMA-376, Second Edition, Part 1 - Fundamentals And Markup Language Reference" I found reporter's reference. No changes here in Third Edition. Reporter's OS unknown, so I modify to WIN (although I assume that it's the same for all) @Andreas J Guelzow: You could increase processing speed and ease our work if your would contribute complete information due to <http://wiki.documentfoundation.org/BugReport> with your reports. So it took more than 1 hour to find the core of your report, what should have taken 5 minutes with a complete report, that would have cost you additional 5 minutes. @Kohei: Please feel free to reassign (or reset Assignee to default) if it’s not your area. Please set Status to ASSIGNED if you accept this Bug. Seems to be an EasyHack? Created attachment 50417 [details] Screenshots, See Comment 2 @Rainer, what additional info were you looking for? I think I described the problem in total: 1) the file contained <TotalTime>1</TotalTime> in /docProps/app.xml 2) LibreOffice interprets this as 1 sec when 3) The standard clearly states that this is 1 minute. What else did you need? The behaviour of other implementations is pretty much irrelevant in this case (and apparently you are using an old version of Gnumeric). A recent version would have shown you all properties in the file. How does my OS matter in this case? And of course it is _not_ MSWindows but Linux. I gather that you are not interested in bug reports so I will again stop filing them. IMO, Andreas' bug report is short and to the point, that contains all necessary information without being too wordy. I'm not a big fan of unnecessary lengthy bug reports which takes time to read, so I prefer bug reports like this one. Just FYI, Andreas is a well-known contributor to Gnumeric, and both Eike and I know him very well from the ODF TC. So, I hope we can treat his bug reports a little more seriously. I see similar problems with .docx Sample document for "Bug 30713 - [FILESAFE]: Images only shown as placeholders in docx" shows Total Editing Time "0 Minutes", LibO 3.4.3RC1 "00:01:55", MAster "00:02:55". I did not find to check the XML <TotalTime> contents. Since all new unconfirmed bugs start in state UNCONFIRMED now and old unconfirmed bugs were moved to NEEDINFO with a explanatory comment, all bugs promoted above those bug states to NEW and later are automatically confirmed making the CONFIRMED whiteboard status redundant. Thus it will be removed. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.