https://bugs.documentfoundation.org/show_bug.cgi?id=159018
--- Comment #9 from Mike Kaganski <[email protected]> --- (In reply to Angelo from comment #6) > I'm sorry if you misunderstood my comment. I understood your comment. Please try this procedure yourself: 1. In a new clean document, change a cell's font to Arial. Alternatively, change default cell style's font to Arial (for the test, it doesn't really matter); 2. Open the Special Character dialog ("Omega" toolbar button, r Insert->Special Character); 3. Select Wingdings font, scroll down till the checkmark, double-click it; 4. Now, when the cell contains the checkmark character, select the character in the cell, and look at the displayed font name. The #4 shows Wingdings, which illustrates my point: our tool not only inserts the character, but also formats it explicitly, as using a specific chosen font. 5. Change another document's cell to Arial; 6. In initial document, select the checkmark (either in cell's edit mode, or the whole cell), and copy to clipboard (Ctrl+C); 7. Paste into the second document (either in cell's edit mode, or over the whole cell). #7 will have all the pasted instances of checkmark to have explicit Wingdings font applied, making this character survive save/reload, version upgrade, etc. My point is: this worked this way (explicitly marking the special character's font) all the way down, even in LO 3.3. Now open your attachment 191759, and inspect your checkmark characters - select them individually, and see the reported font. See that they have a *different* font - namely, Liberation Serif. This shows, that your procedure, or your workflow, included not only the steps you mentioned in comment 3 and comment 6, but also *something* which broke the explicit formatting of this character with the font. Multiple things may do that: clearing cells' direct formatting; saving to file formats that don't support partial cell formatting (like XLS(X)); using special paste (text only); pasting to e.g. Notepad as intermediate place, then copying from there ... only you can (possibly) tell what was that. But all that is not the program's fault. As soon as user's actions removed the explicit "this is Wingdings!" mark from the character, these characters become subject to the pure luck of accidentally choosing the expected font (or not). As I said, the real bug could be, if Calc would *not* itself mark the inserted character using correct font initially. Also, a bug would be, if normal paste of a copied correctly formatted character would drop the formatting. Another possible bug could be, if saving to ODS would drop the formatting. But I don't see any of the three in the versions I tested so far. The only phenomenon I observe is "expected" (accidental) choice of *fallback* Wingdings font for your (unformatted!) checkmarks in 7.4 and some earlier, and (normal, not a bug) choice of a different fallback font in 7.5.0+. (In reply to ady from comment #8) > Regression? This is already answered in comment 2. This doesn't looks like a regression. I marked it "needing bisection", to learn which exact commit created the fallback font choice difference - not because it looks like a bug, but because it *could* be an unintended side effect, in which case there could be a potential fix. > Should this report be set as NEW? No until either: 1. A bisection proves that the change was unwanted side effect; 2. Angelo provides steps to show how LibreOffice looses the font information. -- You are receiving this mail because: You are the assignee for the bug.
