Created attachment 86752 [details]
Scaling of math symbols (e.g., brackets) is worse in 4.1 than in 4.0.
Created attachment 86753 [details]
Screenshot from 184.108.40.206
Created attachment 86754 [details]
Screenshot from 220.127.116.11
Created attachment 86755 [details]
ODT as rendered in 18.104.22.168 from "Save as PDF" from OS X print dialog
Created attachment 86756 [details]
ODT as rendered in 22.214.171.124 from "Save as PDF" from OS X print dialog
Created attachment 86757 [details]
ODT as rendered in 126.96.36.199 from native "Export as PDF"
Note: I was unable to do a native "Export as PDF" from 188.8.131.52 as LibreOffice kept crashing before the export could complete. The crash is probably captured by bug 67660.
I'm not sure how widespread use of the Formula Editor is, but I'd like to lobby for inclusion of this bug (or at least this symptom) in bug 60270 (most annoying 4.1 bugs) or bug 65675 (most annoying 4.2 bugs) as appropriate.
Cannot reproduce with 184.108.40.206 under Win7x64 -> MacOS specific?
Looks like an absent font issue. Packaging problem?
I do not reproduce with LO 220.127.116.11.0+ under Ubuntu 13.04.
Please, could you try again using LO 4.1.2 RC3 when it will available in few days?
Best regards. JBF
I think it is a case of different font being used. The math symbols are taken from OpenSymbol font, and 4.1 had a bug that caused the internal version of the font to not be made available to LibreOffice.
This should have been fixed as part of bug 68192. To verify that it is the same issue, try installing the OpenSymbol font system-wide (it should be under share/fonts/truetype/ somewhere in the LibreOffice.app, too lazy to fire up my Mac to check it).
I copied the opens___.ttf file from LibreOffice.app/Contents/share/fonts/truetype/ to my ~/Library/Fonts directory and restarted LibreOffice with my test document. It appears to address the issue.
I have marked this as a duplicate of bug 68192, but please override that if a different resolution or status is required (e.g., for regression, etc.).
*** This bug has been marked as a duplicate of bug 68192 ***