-
Notifications
You must be signed in to change notification settings - Fork 820
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
xlsx produces corrupt file that cannot be opened from Excel but can be opened from Libreoffice. #609
Comments
@Splizard these things almost always occur because Excel is extremely picky about the XML it will or won't accept, whereas LibreOffice tends to say "Valid XML is Valid XML". I have theories about why that's the case, but they don't really matter - we consider these cases to be bugs. |
Stale issue message |
Stale issue message |
Hello! Will this change be included in the next release? |
@mzt14 it's in the 3.2.4 milestone. I honestly don't know when that release will be. For transparency, I don't use this library and I haven't done for a long, long time. Since it stopped being part of my day job in 2011, I've done a lot of work on it in my own time, as have a handful of other people. I have very little time to commit to this at the moment. Honestly, this project desperately needs some of its many users to become active contributors. |
This is believed fixed by #681. Can anyone confirm? |
I'll see if I can check this, cheers @tealeg |
The problem still exists today |
@confirm2315 OK, thanks for the confirmation. On the master branch, right? Not the release. |
@tealeg Yes, on master. Excel shows blank lines starting with the last added one |
Stale issue message |
Hi, I am working on a program that copies data from three different source spreadsheets into a final spreadsheet.
Here is a sample of the kind of processing involved:
CopyCell is defined as:
However the output file is always corrupted and cannot be opened in Excel.
I imagine this is a bug, any idea why this is happening?
The text was updated successfully, but these errors were encountered: