Created attachment 57250 [details] An example file Problem description: When I try to open Excel XML files from LibO Calc (explicitly specifying the Excel 2003 XML file type), an "ASCII Filter Settings" dialog pops up, and the XML file is opened in LibO Writer as a text file. The same file works perfectly with LibO 3.4.5 and earlier versions on the same machine. I did a clean reinstall with 3.5.0, removing 3.4.5 first. Steps to reproduce: 1. Start LibO Calc 3.5.0. 2. File/Open/set file type to "Microsoft Excel 2003 XML" 3. Select attached file. 4. Press OK on the ASCII Filter Settings dialog. Current behavior: Opens as text file in LibO Writer. Expected behavior: Opens as a spreadsheet in LibO Calc. Platform (if different from the browser): Browser: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20100101 Firefox/10.0.2
There might be some problems with the attachment. I've tried it with LibO 3.4.0 and that version did not open it. (No ASCII Filter dialog, no XML text in Writer, only an empty Writer document.)
The same problem for me. I tried this with win 7 x64, win xp x86, Mac Snow Leopard and Lion. Work fine with LibO 3.4.5 for me too.
Still not working in 3.5.2.
Problem still there in LO 3.6.0.0beta3+ If try to insert the bugdoc in a sheet, I get the following error message in the terminal : Entity: line 1: parser error : Start tag expected, '<' not found ineStyle="Continuous" ss:Weight="1" ^ Steps to reproduce: - start LO in a terminal - open a blank spreadsheet - menu Insert > Sheet from a file - choose the xml file previously saved on the HD Tested under Ubuntu 11.10 x86_64 Version 3.6.0.0.beta3+ (Build ID: eba3ef8) Markus or Kohei: please, could you have a look? Best regards. JBF
Seems to be a duplicate of bug 35078.
Just FYI, I have zero interest in fixing the current XSLT-based filters, which this one is. My opinion is to just disable all XSLT-based filters altogether, including Excel 2003 XML.
IMO we should write a real C++ filter for this *if* Excel 2003 XML is truly worth it.
I had the same issue and when I was going to open a new case I have seen that it is already openend here. I have put in dropbox two examples, One that open because it is a small file: http://dl.dropbox.com/u/30880870/prueba.xls One that won't open becuase it is big: http://dl.dropbox.com/u/30880870/prueba2.xls I have tested with the same behaviour in XP and W7. and in LibreOffice 3.5 and 3.6.0.4
Removing the byte-order-mark from the example file attached to this report allows the file to be successfully imported again (3.5.4 debian wheezy packages). This is a regression compared to previous versions of OpenOffice.org where the exact same file is imported correctly. (And please don't rip out support for file formats that people are using -- I've been able to push the adoption of libreoffice based on the support of this format and if this format disappears, I am unlikely to have the resources to develop support for some other spreadsheet format and would sadly end up having to recommend alternatives instead.)
*** Bug 70631 has been marked as a duplicate of this bug. ***
Maxim Monastirsky committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=f38277dc0337df15f3ea689096a2c18a03354a61 fdo#46262 Detect XML files with UTF-8 BOM The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
This particular case of a file encoded as UTF-8 with BOM is fixed with the above commit. There is still a problem with detecting UTF-16 files, but that belongs to Bug 35078. (In reply to comment #8) > One that won't open becuase it is big: > http://dl.dropbox.com/u/30880870/prueba2.xls I can't reproduce it with LO 4.1.3.2 & master builds under Ubuntu 13.10 & Win7. One problem that might be with large files is Bug 65980, but this file opens for me in ~10 seconds, so it's surely not the case. Anyway this file is ISO-8859-2, so you should open a new bug report if you still have this problem.
*** Bug 60336 has been marked as a duplicate of this bug. ***
This may be a window problem I guess when I am not able to access my excel on my Pc. So I contact https://babasupport.org/microsoft/windows-customer-service/150 which help me in this.I love to share this with all of you hope it is helpful.When I get an attachment problem and other excel your article helps me more.