Created attachment 146669 [details]
The zip contains the screen record video and the sample file.
If I open a xlsx file with cell comments in Calc and save it, and then open it back in Excel, at first glance nothing changes but only the color of the comment box (changes from the yellow to white).
But if I do a save&open routine in Excel again, the comments get completely broken - instead of floating rectangle box a massive round arrow is seen with the comment text underlying.
I recorded a short video showing the steps:
1. Created a new empty file with a random comment, saved as xlsx&closed.
2. Opened it with the Calc, saved & closed.
3. Opened it again in Excel (color changed to white, but it's still okay), saved & closed
4. Once more opened in Excel and you can see the comment messed up.
Version: 22.214.171.124 (x64)
Build ID: 65905a128db06ba48db947242809d14d3f9a93fe
CPU threads: 4; OS: Windows 10.0; UI render: default;
Locale: ru-RU (be_BY); Calc: CL
MS office 2016 Pro
Tested this situation also in the most recent 126.96.36.199.aplha1+ build (2018-11-15_23:05:09) - the arrow bug persists.
The only difference I see is the comment box color - it does not change its color to white (as it was in 188.8.131.52) and remains yellow (both in Calc and Excel).
don't repro for
LO 6.2 alpha 1 and MS Excel 2010
I do repro with LO 6.2+ and MSO 2016.
But it looks like "NotOurBug".
Because LO opens file OK and it's MSO that opens wrong file it saved.
I'll close. If you disagree, please explain and set Unconfirmed.
I am reopening this issue for the following reason.
As far as I know MS Excel native file format is extremely wide used for spreadsheets calculations. I even would say it is a de-facto standard (but if this is arguable for someone, I don't insist).
And thus I consider it is vital for the LO to be compatible with the leader and support .xlsx functionality as fully as possible.
Yes, the file visualization gets corrupted in MS Excel (not in the LO) but it really happens only after LO touched the file.
I don't mind if my issue get closed unresolved finally, but please firstly look at it from the point of view I described.
If Excel opens it's own saved file wrong, we cannot know why it does so.
As Roman noticed, doesn't happen with MSO 2010.
Please file a bug with Microsoft.
Still happens with LO 184.108.40.206 and MSO 2013.
Maybe you could take a look at these files? They are tiny and maybe person with knowledge of XLSX format would spot the reason quickly?
This may look like a tiny inconvenience, but actually is a show-stopper if you need to use comments and collaborate with MSO user.
I've found that in my case all it takes to fix the XLSX file after it was saved by LO Calc, is to replace
<v:shape ... type="#_x005F_x0000_t202"
<v:shape ... type="#_x0000_t202"
"_x0000_t202" is value from XLSX before it was saved by LO Calc.
I hope this will enable you to prepare a fix.
Can't say who did it but looks good with daily master LO 7.1+ from https://dev-builds.libreoffice.org/daily/master/current.html and MSO 2016, which updates itself.
Already in LO 6.4 saved XLSX it is:
<v:shapetype id="_x0000_t202" ...>
<v:shape .. type="#_x0000_t202"
Date: Fri Sep 13 08:13:49 2019 +0200
previous source 0701a1838280d4fa9c54ca39f1a5297fe4857a16
author László Németh <email@example.com> 2019-09-12 15:48:35 +0200
committer László Németh <firstname.lastname@example.org> 2019-09-13 07:59:53 +0200
commit c5d37d324cd6d17114c209de1862344ad58a1d93 (patch)
parent 0701a1838280d4fa9c54ca39f1a5297fe4857a16 (diff)
tdf#117274 XLSX export: fix VML comment shape type id
to avoid shape multiplication in a mixed environment.
*** This bug has been marked as a duplicate of bug 117274 ***