Bug 135602

Summary:	Fileopen DOCX: substitute fonts not working on open when odt with Wingdings saved as DOCX in Linux/Mac (OK in Win and OK as DOC)
Product:	LibreOffice	Reporter:	kan <shariqkeen>
Component:	Writer	Assignee:	Not Assigned <libreoffice-bugs>
Status:	NEW ---
Severity:	normal	CC:	aron.budea, buzea.bogdan, stevedee.atwork
Priority:	low
Version:	Inherited From OOo
Hardware:	All
OS:	Linux (All)
URL:	https://ask.libreoffice.org/en/question/259206/docx-compatibility-substitute-fonts-not-working-when-docxodt-saved-as-docx-by-lo/
See Also:	https://bugs.documentfoundation.org/show_bug.cgi?id=122956
Whiteboard:
Crash report or crash signature:		Regression By:
Bug Depends on:
Bug Blocks:	103342, 108769
Attachments:	1.odt image 1 image 2 2.docx 1.odt saved as DOCX in Word

Description kan 2020-08-10 10:17:19 UTC

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/

Comment 1 kan 2020-08-10 10:30:56 UTC

Created attachment 164098 [details]
1.odt

Comment 2 kan 2020-08-10 10:33:04 UTC

Created attachment 164099 [details]
image 1

Comment 3 kan 2020-08-10 10:33:29 UTC

Created attachment 164100 [details]
image 2

Comment 4 kan 2020-08-10 10:34:34 UTC

Created attachment 164101 [details]
2.docx

Comment 5 SteveDee 2020-09-10 02:21:28 UTC

I have been unable to reproduce this bug in the following builds:

Version: 6.4.6.2 (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
Calc: CL

and:

Version: 7.1.0.0.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
Calc: CL

I think this might be MacOS specific as outlined in the ask.libreoffice post.

Comment 6 Timur 2020-11-06 11:49:34 UTC

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.

Comment 7 Timur 2020-11-06 13:39:05 UTC

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

Comment 8 Aron Budea 2022-04-05 03:09:26 UTC

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.

Comment 9 Timur 2022-04-05 07:04:03 UTC

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).

Comment 10 QA Administrators 2024-04-05 03:15:37 UTC

Dear shariqkeen,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword

Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug