search

qax-os / excelize

Go language library for reading and writing Microsoft Excel™ (XLAM / XLSM / XLSX / XLTM / XLTX) spreadsheets
https://xuri.me/excelize
BSD 3-Clause "New" or "Revised" License
17.64k stars 1.69k forks source link

Generated Excel files lose content partially - Error on opening #1859

Closed dkwstream closed 3 months ago

dkwstream commented 3 months ago

Description

Steps to reproduce the issue:

  1. Create an Excel file with your Go application
  2. Open this file with Excel (not LibreOffice) on Windows or on MacOS

Describe the results you received: Excel triggers an error when you open the created file. A popup "Alert..." is displayed saying some content is not retrievable but Excel propose to repair the file and try to get as much content as it can. When repair is done the Excel has lost a lot of formatting (no more colors in cells, ...) that was saved previously. And this is systematic, always the same error with the same "Alert".

Describe the results you expected: No error when opening the file. An Excel file with all of its original formatting

Output of go version:

go version go1.21.3 linux/amd64

Excelize version or commit ID:

2.8.0

Environment details (OS, Microsoft Excel™ version, physical, etc.): Windows and MacOS

xuri commented 3 months ago

Thanks for your issue. Please try to upgrade the master branch code of the Excelize library. If it still doesn't work, please provide a complete, standalone example program or reproducible demo.

dkwstream commented 3 months ago

I followed your previous recommendations and already upgraded the master branch code of Excelize. But the same still occurs.

chinaDL commented 3 months ago

我也是一样的问题....

xuri commented 3 months ago

Hi @dkwstream, @chinaDL. Could you show us a complete, standalone example program or reproducible demo? If you open an existing workbook, please provide the file attachment without confidential info.

xuri commented 3 months ago

Hi @dkwstream, @chinaDL. There are still not have enough info of code and attachments to reproduce this issue, so I'll close this issue, if you have any questions, please let me know to reopen this anytime.