Created attachment 63358 [details] Excel file with list of companies and their respective financial data Problem description: When opening the excel file "REON-Table.xls" the sheet is empty. No error message. The same excel file contains numbers and text when opened in MS Excel. Please find the file in attachment. Steps to reproduce: 1. Start LibreOffice Calc 2. File->OPen 3. Select REON-Teble.xls Current behavior: progress bar shows when opening file. then no data are displayed Expected behavior: to show the data available in the file Platform (if different from the browser): Ubuntu 10.10 Browser: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:13.0) Gecko/20100101 Firefox/13.0.1
In 3.5, cells with numbers are still not imported.
Created attachment 63628 [details] screenshot On pc Debian x86-64, with master sources (future 3.7) updated today. LO asked about Import Options (Select the language : automatic or Custom, I chose Automatic) + Detect Special Numbers (I tried with option unchecked then checked, same result) Then I got the result of the screenshot. Did you have the same result ?
I get just empty sheet in Ubuntu 11.10, LibreOffice 3.4.4. Even the screenshot (attachment 63358 [details]) shows incomplete import since the table is filled with numbers for all columns and rows in Excel
In fact, Calc behaves correctly. This XLS file is really HTML. It contains one huge table and has empty <td> tags (table cells) where numbers ought to be. Some moron at Microsoft decided, that instead of exporting numbers to <td> content (so any HTML-compliant app could read them), they will write them in x:num attribute. Of course x:num is NOT correct HTML attribute and Calc - as every good-behaving user agent should - ignores them. You may try downloading file attached by Marek Ozana, renaming it to "REON-Tables.html" and opening in web browser. Table will be mostly empty, as in Calc. So, while Calc behavior is correct and expected, it can lead to interoperability problem. This particular file declares to be created by MS Office Excel 2003 (which is rather old), but: a) who knows how many "XLS" files like this are there on the wild b) who knows whether newer Excel versions are saner I am changing title of this bug, so it will show point of this bug more accurately.
We are having quite a few issues because our bank refuses to upgrade their Office or use any format other than xls (we suggested csv)... Can you suggest some work around? Can I write a plugin that taps into the file when it is being open, to extract the xnum attribute as a value?
Kohei/Markus/Eike: would 1 of you have some time to give his opinion about this? Is it a bug, an enhancement?
There's also "x:fmla" attribute which isn't imported too.
(In reply to comment #5) > We are having quite a few issues because our bank refuses to upgrade their > Office or use any format other than xls (we suggested csv)... > > Can you suggest some work around? Can I write a plugin that taps into the > file when it is being open, to extract the xnum attribute as a value? You can fix it in the Libreoffice source code. If you are interested I'll add some code pointers. But be warned that our html parser is one of the worst in the world and it might be easier to write a clean new one based on orcus interfaces. Actually this is a plan for some time now but we just don't have enough time for all this work so it would be awesome if someone here would help.
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (4.4.1.2 or later): https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-03-03
*** Bug 89939 has been marked as a duplicate of this bug. ***
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.0.5 or 5.1.2 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-04-16
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.2.7 or 5.3.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170522
The file in question is an HTML file, not MSO-XML2003 file.
Dear Marek Ozana, 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Well, I submitted a patch for the x:str tag attribute, for bug 96499: https://gerrit.libreoffice.org/c/core/+/123620 but I then abandoned it myself because I thought it was a misunderstanding of the x:str. Now I see this x:num and x:fmla you are discussing here. Is there any documentation show the usage of these attributes? Are there any other attribus like this? Should it be x:str="somestring", or just a blank attribute? What's inside x:num? Without this kind of knowledge it hard to implement correctly.
Dear Marek Ozana, 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