-
Notifications
You must be signed in to change notification settings - Fork 808
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Investigate "Unreadable content" Issue #38
Comments
If it helps, I got around this using the following code;
|
I don't think blindly removing workbook parts is a good fix. There might be instances where a user really wants those parts. Let's rather try figure out the underlying issue. Am I correct in saying that the problem is that ClosedXML generates files that open correctly on both Excel 2010 and Excel 2013 the first time. But when the files are then saved in Excel and reopened, Excel 2010 is unable to do so, but Excel 2013 can do that? I read the original thread on Codeplex, but I'm unable to see a consistent reproduction of the error. People over there are mentioning all kinds of manifestations. If we can get a unambiguous set of steps to reproduce the problem, we can fix it. In the meantime, I'm hunting down a copy of Office 2010. |
Sorry, try as I might, I'm unable to reproduce it now, using either 2010 or 2013. I even rolled the ClosedXML version back to 72.3, which I was using back then (it was in 2014). It was consistent however, hence the code to work around. The details of the error were; From memory, the issue was that the styles.xml file referenced the extension x14 at the start and defined it at the end; ie <x:styleSheet xmlns:x14="http://schemas.microsoft.com/office/spreadsheetml/2009/9/main" ... <x:extLst><x:ext xmlns:x14="http://schemas.microsoft.com/office/spreadsheetml/2009/9/main" uri="{EB79DEF2-80B8-43e5-95BD-54CBDDF9020C}"> But when saved in 2010, the reference at the start would be dropped and excel would have problems opening it. I found that deleting all the extLst elements solved the problem and didn't cause any issues. I assume excel recreated them where required. Being that I can't recreate it, perhaps an Office update managed to fix the issue...? |
OK we will close this for now :) |
Yeah, one guy said applying KB2889836 solves this issue in Excel 2010. Maybe that really was the case. |
https://closedxml.codeplex.com/workitem/8466
The text was updated successfully, but these errors were encountered: