https://bugs.documentfoundation.org/show_bug.cgi?id=159018
--- Comment #7 from ady <[email protected]> --- FWIW, for me, on MS Windows opening attachment 191759 from comment 1 with: * LO 7.5.3.2 shows the check mark * LO 7.6.3.2 shows a different character * AOO 4.1.14 shows a different character (which looks the same as in LO 7.6.3.2). I have not tested LO versions between 7.5.3.2 and 7.6.3.2. This range might give a clue for bibisecting. Using Calc's UNICODE() function in order to identify the character seems useless in this case. Anyway, using UNICODE() on the character, it shows decimal 61692, hex F0FC (part of the "Private use" range). In the Insert Special Characters dialogue for Arial, and for Liberation Serif fonts, such Unicode (61692) is not included. Using LO 7.6.3.2, I copied the character to another workbook. On the cell where the character was pasted, changing the font to Wingdings shows the check mark again (instead of the other character). Whether the specific font is actually set within the (part of the) cells for the specific inserted character, I have no idea. With LO 7.6.3.2, I can save a new file containing the Windings character mixed with some other characters using a different font in the same cell. Opening it shows the same Windings character. This suggests that the problem shows up when opening a file that was saved with an older version. It looks as some kind of font replacement change, at some point after LO 7.5.3.2. Considering prior comments, I am unsure which exactly is the bug, or whether there is one. If it wasn't for those comments, I would be setting this report to NEW. At any rate, from the POV of the user, the file (as-is) seems not future-proof. Even re-inserting the check mark character anew, is there any way to avoid this problem happening again (perhaps at some additional change in fonts replacement)? -- You are receiving this mail because: You are the assignee for the bug.
