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
There seems to be an issue with shared strings. When opening the file from #186 I get some strange warning in Excel. I have a similar warning if I load and open the xlsx file from this issue: ycphs/openxlsx#81 (this one is about styles.xml)
Unfortunately both files have a huge shared strings table. I've tried to find something but had no luck. Might be something our parses does to the file, but I'm quite clues at the moment.
Iirc copying sharedstrings.xml solved this, but if that's the only solution, we'd never be able to write shared strings.
The text was updated successfully, but these errors were encountered:
Replacing self$shareStrings with a custom created sst has no error in the shared strings table anymore, it must be something else. Maybe some tag is written as <foo/> and Excel expects <foo></foo> or some strange unicode encoding thing? Theres another issue with some broken cell, but lets ignore that for a minute :>
There is a remaining warning, when opening the file from #186. Excel complains that one or more cells on sheet 2 are damaged. Unfortunately its a 31564 x 52 data frame and even vscode complains that the filesize of sheet2.xml is a bit large. No clue where or what to look for. Numbers reads the file without any complains.
There seems to be an issue with shared strings. When opening the file from #186 I get some strange warning in Excel. I have a similar warning if I load and open the xlsx file from this issue: ycphs/openxlsx#81 (this one is about styles.xml)
Unfortunately both files have a huge shared strings table. I've tried to find something but had no luck. Might be something our parses does to the file, but I'm quite clues at the moment.
Iirc copying sharedstrings.xml solved this, but if that's the only solution, we'd never be able to write shared strings.
The text was updated successfully, but these errors were encountered: