Apache OpenOffice (AOO) Bugzilla – Issue 124203
Appearance of symbols in formula during GUI are not equal for Windows 7 and Windows 8
Last modified: 2020-01-17 14:33:46 UTC
Created attachment 82532 [details] Comparison between Windows 7 and Windows 8 formulas Formulas are not shown as supposed to in GUI running on Windows 8. The fonts appear to be different from the ones used in Windows 7. It occurs all over OO products. Its occurrence can make users to stop using OO impress, since a scientific presentation requires formulas to be shown properly. Nevertheless, pdf files made with built-in Export as PDF (with default settings) work fine in both Windows versions.
It could be that the two different systems have different sets of fonts installed. Please provide the resulting PDF for each so that we can see in its font properties which ones were actually used.
Created attachment 82783 [details] OO 4.0.1 Write files and Pdf files on Windows 7 and Windows 8.1 Thank you for any answers, I submit OO 4.0.1 Write files and Pdf files (created with built-in Export as Pdf) on Windows & and Windows 8.1.
*** Issue 126666 has been marked as a duplicate of this issue. ***
Windows OS at 8, 8.1 and now 10 are pulling the symbols for the Operators for the Math formula editor from system "Segoe UI" & "Segoe UI Symbol" font--rather than from the OpenSymbol font. For now, as a workaround on Windows, able to apply a font substitution. Tools -> Options -> Fonts: Replacment Table and replace always OpenSymbol with Cambria Math, it has a better appearance than the Segoe UI Symbol font.
This bug has been solved in LO. It hasn't been solved directly as the bug were reported and no one took care about it. It may have been solved by a side effect of a commit. The resolution appeared between LO 5.3 alpha1 and LO 5.3 beta1 I guess this commit could be the solution : https://cgit.freedesktop.org/libreoffice/core/commit/?h=libreoffice-5-3&id=641b9cb1d0934b3f8b4a80279cb3f3f81ecc4707 If this could be of any help
(In reply to choffardet from comment #5) > [...] > > If this could be of any help Only when you can convine the author of the patch to provicde it also under ALv2. Otherwise the license doesn't fit and the patch cannot be used.
" Only when you can convine the author of the patch to provicde it also under ALv2. Otherwise the license doesn't fit and the patch cannot be used. " Does it mean that if this commit is the solution to this bug, you can't solve this bug until this commit is provide under ALv2 licence ? You can't do something like this commit, something better or worse ? First of all, we should know if this commit is the solution and then searching a way to apply it.
(In reply to choffardet from comment #7) > " > Only when you can convine the author of the patch to provicde it also under > ALv2. Otherwise the license doesn't fit and the patch cannot be used. > " > Does it mean that if this commit is the solution to this bug, you can't > solve this bug until this commit is provide under ALv2 licence ? right. Just copy & paste would be illegal. > You can't do something like this commit, something better or worse ? > > First of all, we should know if this commit is the solution and then > searching a way to apply it. You could help us in verifying this: Check out the current code, apply the patch, build and check if the bug is gone. Then we are sure and could try to find an alternative solution.
"You could help us in verifying this: Check out the current code, apply the patch, build and check if the bug is gone." Be sure that I would have done it before posting in this bug if I had the knowledge to do such a task But sadly I'm not a dev.
I'm pretty sure Khaled would grant the license, I've cc'd him. However, to be kind there is tremendous "technical debt" across the AOO SVN to be met to bring the AOO font rendering current enough for this to have any applicability. Otherwise the work around from comment 4 remains valid for folks working on Windows 8, 8.1 or 10
The commit referenced in comment 5 fixes code that does not exit in AOO, so it is unlikely to have relevance to any AOO bug.
A forum post to this Issue: https://forum.openoffice.org/en/forum/viewtopic.php?f=12&t=85801&hilit=sqrt
*** Issue 125982 has been marked as a duplicate of this issue. ***
*** Issue 128266 has been marked as a duplicate of this issue. ***