In a weird MS gotcha, seems that Windows 8.1 and 10 have somehow been substituting Segoe UI in Math formula editor when the formula Operator's "prod", "sum" and "int" are used. Windows 7 sp1 installs are not affected. Weird in that "coprod" and "lint" are unaffected, as are the "iint" and "iiint" and variants of "lint".
Created attachment 120632 [details] sample formula with incorrect Segoe glyps used for operators STR Enter this as an example formula in Math on a Windows 8.1 or Windows 10 install. "prod %PI sum %SIGMA int iint coprod a" the %PI and %SIGMA render correctly in OpenSymbol, as do iint and coprod. Screen clip attached.
Created attachment 120633 [details] screen clip of test formula in 4.3.7 on Windows 8.1 Looking at an /a install of 4.3.7.2 run on Windows 8.1, in addition to "prod" and "int", "coprod" and the "lint" are rendered in Segoe UI system font--but strangely the "sum" operator picks up OpenSymbol. clip attached.
(In reply to V Stuart Foote from comment #2) > font--but strangely the "sum" operator picks up OpenSymbol. > > clip attached. Actually the capital SIGMA there is not from OpenSymbol different weights on the leg and the serif--reviewing in BableMap--it looks like it and all of these symbols are from MS "Seoge UI Symbol" font. That I guess would make more sense but is it the behavior we want?
Looking at BableMap--the Segoe Symbol UI being used is pulling from the Mathematical Operators page at Ux2200. We get Ux220F for N-ARY PRODUCT, and Ux2211 for N-ARY SUMMATION. OpenSymbol has the same page defined--so not clear why Windows 8.1 and Windows 10 are using Segoe Symbol UI instead of OpenSymbol which is present on the system(s).
Until this can be corrected, as this affects Windows users only, a reasonable work around is to perform a LibreOffice font substitution (Tools -> Options -> Fonts): replacing OpenSymbol with Cambria Math -- a font present on all MS Windows releases since MS Vista. @Andras, noticed in bug 76239 (though that OpenSymbol install issue is not related to this at all) that you're working in Windows 8.1--any thoughts here about OS' Segoe UI font selection and non-use of OpenSymbol for specific dialogs?
Spent more time in the font charts using BableMap -- so the only symbols being assigned from Segoe UI rather than OpenSymbol are where the font glyph actually exists in Segoe UI (v 5.53 on Windows 10). Unfortunately that is not a full set of glyphs for the Mathematical Operators Unicode block. Those are defined in Segoe UI Symbol, but those are not pulled. Result in LibreOffice (and AOO) is a mix of OpenSymbol and Segoe UI in formula, unless a font replacement is specified for OpenSymbol, which itself is weird. Leading to the development question "Why are MS Windows 8, 8.1 and 10 substituting the system front for our OpenSymbol usage?" and "How do we prevent it?".
My result matches attachment 120632 [details] Win 8.1 32-bit Version: 5.2.0.0.alpha0+ Build ID: 51a5dfd783bfc1efc52a791aab4114039581252f Threads 4; Ver: Windows 6.2; Render: default; TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2015-12-04_10:49:33 Locale: fi-FI (fi_FI)
*** This bug has been marked as a duplicate of bug 60268 ***