Corrupt Excel file when using an ampersand in a table header about fastexcel HOT 8 CLOSED

Thanks for your feedback, I think I have fixed this issue, but the release date is not guaranteed

from fastexcel.

A temporary solution is to escape special characters beforehand.

...
worksheet.range(0, 0, row - 1, getDataRow1().size() - 1).createTable(escape(toArray(getHeadersCorrupt())))
                    .styleInfo().setStyleName("TableStyleMedium3");
...

...
    private String[] escape(String[] stringArray) {
        for (int i = 0; i < stringArray.length; i++) {
            stringArray[i] = XmlEscapeHelper.escape(stringArray[i]);
        }
        return stringArray;
    }
...

from fastexcel.

Hi Tom,

thanks for your investigation and reply.

Unfortunately, your suggested solution doesn't work. I had already tried to replace the ampersand with the escaped characters &. If I do this, the error message still comes up when the excel file is opened, and the header doesn't show the ampersand, but the escaped sequence.

Also, using your escape method (which seems to do the same for the ampersand), doesn't help. (I had to modify your solution slightly to "new XmlEscapeHelper().escape(.)", as the method is not static.

Best,
Holger

from fastexcel.

I'm not sure if you've applied the correct escapes because I can't see your code. In my test, the & is translated to &,and stored in the table1.xml file. You can change the suffix of the generated xlsx file to zip, then unzip it and check the xl/tables/table1.xml file. Check the name property on table>tableColumns>tableColumn to see if the & is correctly escaped.

from fastexcel.

Yes, the & is translated to & , and I can see it in the table1.xml file (I always investigate it with 7zip). But that doesn't make the error disappear.
Have you tried your solution with my sample project I created?

from fastexcel.

I just checked the code, and in the latest released version 0.18.0, the XmlEscapeHelper().escape(.) method is indeed not static. I have submitted the code to make changes to this a few months ago. This change is already in the latest code of the master branch, but when it will be released depends on the project owner.

from fastexcel.