I have a docx file, coming from MSO [probably not, see update below] directly without any editing from LO, containing tick and cross symbols from Wingdings 2 as shown in image 1. Wingdings 2 is not available but it's being substituted effectively as in image 1. utf-16 codes for characters are U+f050 and U+f04f.
observation1: If i make any change to this docx, even if not touching these symbols, and save as docx using LO [2.docx], then it is not being substituted correctly anymore as shown in image 2 upon reopening the 2.docx. Also happens if I use safe mode to edit and reopen.
observation2: But if i make changes to original docx file and save as odt instead of docx, then substitution is working ok, until I save it as docx.
Lot more details at https://ask.libreoffice.org/en/question/259206/docx-compatibility-substitute-fonts-not-working-when-docxodt-saved-as-docx-by-lo/
Created attachment 164098 [details]
Created attachment 164099 [details]
Created attachment 164100 [details]
Created attachment 164101 [details]
I have been unable to reproduce this bug in the following builds:
Version: 184.108.40.206 (x64)
Build ID: 0ce51a4fd21bff07a5c061082cc82c5ed232f115
CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: GL; VCL: win;
Locale: en-AU (en_US); UI-Language: en-GB
Version: 220.127.116.11.alpha0+ (x64)
Build ID: fb8334aa79e811bb6780e072e24d2580932f1031
CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win
Locale: en-AU (en_US); UI: en-GB
I think this might be MacOS specific as outlined in the ask.libreoffice post.
DOCX attachment 164101 [details] is LO saved (seen if unzipped) so not relevant as a source.
It's good to follow Ask but you need to review what's written there, not just copy. I don't have time to read all.
This is confusing report, please write exact steps.
And test with master from https://dev-builds.libreoffice.org/daily/master/current.html.
This bug is Linux only and DOCX only, OK in Win and with DOC.
1. Open ODT attachment 164098 [details]
2. Save as DOCX
Experienced: wrong open of Wingdings in LO and good in MSO
Created attachment 179312 [details]
1.odt saved as DOCX in Word
There's a FILEOPEN aspect of this bug as well, see 1.odt that was saved as DOCX in Word, it doesn't show the correct symbols when opened.
Simple workaround is to replace Wingdings for OpenSymbol in Options-Fonts table.
I shared my table in bug 64509 as attachment 167165 [details].
When there's no Wingdings in Linux, who knows what LO replaces it with (bug 61134).