Bug 128675

Summary:	Error export formula in MS office 2007~2019 format
Product:	LibreOffice	Reporter:	Army_bloodcore <army_bloodcore>
Component:	Formula Editor	Assignee:	Not Assigned <libreoffice-bugs>
Status:	RESOLVED DUPLICATE
Severity:	minor	CC:	vsfoote
Priority:	medium
Version:	6.2.0.3 release
Hardware:	All
OS:	Windows (All)
Whiteboard:
Crash report or crash signature:		Regression By:
Bug Depends on:
Bug Blocks:	39750

Description Army_bloodcore 2019-11-08 16:00:50 UTC

Description:
When I am typing formula and exporting it in MS office 2007~2019 format, it becomes a wrong font.

Steps to Reproduce:
1. Create document in LibreOffice
2. Type any formula
3. Save document in MS office 2007~2019 format (*.docx)
4. The result font in MS office will be cambria math

Actual Results:
Formula font must be that I've been setted up.

Expected Results:
Formula font is cambria math.


Reproducible: Always


User Profile Reset: No



Additional Info:
[Information automatically included from LibreOffice]
Locale: ru
Module: TextDocument
[Information guessed from browser]
OS: Windows (All)
OS is 64bit: no

Comment 1 V Stuart Foote 2019-11-08 19:13:28 UTC

Any better for you if you force LibreOffice to substitute Cambria Math for OpenSymbol.

Tools -> Options -> Fonts  and 'Apply replacement table' checkbox

enter OpenSymbol in the 'Font' droplist, and Cambria Math in the 'Replace with' droplist. Then use the green check mark button to create the replacement entry.

Check 'always' checkbox, and OK to complete the dialog.

Substitution should apply to the GUI, and to any output/printout.

Until bug 101174 is implemented, this should work.

Comment 2 Army_bloodcore 2020-02-18 12:22:31 UTC

I tried that way, and this problem has no solved. With export in *.doc (MS Office 1997~2003) format, there is all right, font saves, but when I am trying to save in *.docx, fonts are ruining. I decided to simplify my documents and make it maximum free from formulas objects to improve compatibility between MS office and LibreOffice. It will take some time.

Comment 3 Timur 2020-02-18 15:01:58 UTC

I confirm the behavior-
But that seems to be a consequence of bug 119170.

*** This bug has been marked as a duplicate of bug 119170 ***