https://bz.apache.org/ooo/show_bug.cgi?id=127021
--- Comment #8 from orcmid <[email protected]> --- (In reply to [email protected] from comment #7) > "Was the original file produced by some software means other than from Excel > itself?" > > Yes, it was. We used 3rd party library (from axolot) to be able to produce > excel for other users. It appears that there is some sort of edge case in the production from the third-party library that trips over a situation AOO Calc was never designed nor tested for and now results in excessive conversion time in Calc. It could also be that there are discrepancies related to what version of the OOXML spec is being produced against by the third-party software. This is a classic interoperability problem and, while it can be considered a defect in the AOO implementation, there is really no way we can get to that with such gigantic files. I think the important consideration is that there is little chance of a change in Apache OpenOffice XSLX import in the foreseeable future. You might consider a workaround if it is important to open those files in Apache OpenOffice. In particular, using Microsoft Office to open the .xlsx and save it in .xls format should provide a remedy so long as unique features of .xlsx are not being depended upon. (An alternative would be to endure the incredibly-long file-open time and then save the result as a .xls or even .ods from Calc. But I think using Excel to do the .xlsx -> .xls is more likely to maximize fidelity as well as being much quickler.) -- You are receiving this mail because: You are the assignee for the issue.
