-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
Cell that contains <![CDATA[xxx]]> is not interpreted #79
Comments
Thanks for your report! Please ensure you have provided enough info in order to recreate the issue, including the problematic ODS File. |
I tried to insert a SODS returns "Column 1" which it's the expected result. Whatever your problem is, it's not related with the CData modifier. I need a way to reproduce it... Maybe you can make a copy of the file, delete all the rows content and post it here? A minimum viable example of 1 row is good enough. |
I tried to reproduce a file. The original file is from a client so I'm not really sure how they ended up with that because if I re-save it in libreOffice so anonimise the rows the import it's fine 🙈 I hope it works (or I mean doesn´t work as well) with you. |
@Lb-lea should be fixed in 1.6.4 |
Hello,
I am trying to read a file produced by Excel and the header cells contains the
<![CDATA
markupThe headers basically looks like that (albeit simplified)
However in the sods SpreadSheet created with the file, the first row only contains null column. The other rowns are fine since they don´t have the cdata tag.
I have re-saved with LibreOffice and this time the cdata markup is gone and sods reads my file just fine.
I thus conclude that the cdata is what is preventing the cell values from being loaded.
After looking it up it turns out that the cdata markup marks data that contains character that could be interpreted as xml but should not.
Thus I think sods should be able interpret my cells as text values.
SODS version 1.6.2
As for providing a full file, sadly the file I have contains confidential data and I cannot reproduce the bug myself while trying to create a clean speadsheet on Excel
The text was updated successfully, but these errors were encountered: