You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Then open the resulting file with Office for Mac results in the following warning:
If you click "Open and Repair" the file will open but be displayed with no styling and a prompt as follows:
If you click "View" to see the log you'll see:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<recoveryLog xmlns="http://schemas.openxmlformats.org/spreadsheetml/2006/main"><logFileName>Repair Result to hello1050.xml</logFileName><summary>Errors were detected in file '/Users/bruce/Work/viewprogis/viewprogis_web/vpg/hello105.xlsx'</summary><removedParts summary="Following is a list of removed parts:"><removedPart>Removed Part: /xl/styles.xml with XML error. (Styles) Load error. Line 36, column 36.</removedPart></removedParts><repairedRecords summary="Following is a list of repairs:"><repairedRecord>Repaired Records: Cell information from /xl/worksheets/sheet1.xml</repairedRecord><repairedRecord>Repaired Records: Cell information from /xl/worksheets/sheet2.xml</repairedRecord></repairedRecords></recoveryLog>
Suggesting a problem with xl/styles.xml
I think I have found a solution and will submit a pull request soon.
The text was updated successfully, but these errors were encountered:
Thanks for the great project!
This can be reproduced by creating the simplest possible file then trying to open it in Microsoft Excel for Mac (https://products.office.com/en-ca/buy/compare-microsoft-office-products?tab=tabs-2).
For example if you run the example from the readme:
Then open the resulting file with Office for Mac results in the following warning:
If you click "Open and Repair" the file will open but be displayed with no styling and a prompt as follows:
If you click "View" to see the log you'll see:
Suggesting a problem with
xl/styles.xml
I think I have found a solution and will submit a pull request soon.
The text was updated successfully, but these errors were encountered: