Mike Kaganski pointed out in bug 99402 that the symbol font handling in Linux wasn't done properly in the first place:
"The Symbol font that is shipped with Windows (and is used in WMFs) has Symbol charset (see https://www.microsoft.com/typography/fonts/font.aspx?FMID=1650). OpenSymbol, on the other side, only has 1252 Latin-1 charset in it.
Fixing the original Linux problem by forcing Win1252 codepage everywhere seems to work, even under Windows (at least my Win10 shows it well; seems that Windows somehow makes internal recoding here). But I'm not sure if that's a correct solution. IMO, more correct solution would be adding the Symbol charset to OpenSymbol font itself."
(see full comment at )
Currently empty rectangles are displayed instead of brackets in mathtype formulas.
"Under Linux, after the regression is fixed, the attacment 124514 from comment 0 shows two problems: one with brackets, and another one with "h" with stroke in second line in h^2/2m. Both problems are caused by absent fonts: brackets - from Symbol; stroked h - from MT Extra. Symbol font is mapped to OpenSymbol under Linux. (I only mention MT Extra here for completeness/reference; it's out of scope here.)"
(also from , attachment is )
Setting to NEW, as this is a confirmed issue.
Behavior can be fully seen with 5.3 master builds that include this commit (but some brackets were already wrong before the regression in bug 99402 was introduced):
tdf#99402: fix Metafile Font handling
Mike, thanks for your analysis in bug 99402, here's the new bug report as requested. Please adjust component if a different one is more suitable.
This problem is described as #6 in bug 39256.
As that bug looks more like a meta-bug for tracking WMF-related problems, I add it as "See Also" and will work on it here.
Further analysis shows that my previous statements need correction.
1. Always using 1252 doesn't work for Windows; I must had been dreaming when wrote that it worked under Win10. So, the only way to fix this by selecting encoding is conditional compilation (symbol charset for Windows, 1252 for Linux).
2. OpenSymbol doesn't contain necessary glyphs for brackets/braces/parentheses. Standard Symbols L actually does. When Symbol font encoding is set to 1252, Standard Symbols L is used by LO, while for symbol encoding, OpenSymbol is used, with recoding using utilities from unotools/source/misc/fontcvt.cxx. I see preferable way to fix this by enabling LO to substitute Standard Symbols L for Symbol font when symbol charset is used.
3. MT Extra problem mentioned above (and in bug 39256 #6) is fixed by using symbol encoding, works both for Windows and Linux (MacOS isn't tested).
It's not that straightforward to fix the font substitution.
The actual used font is selected in ImplFontCache::GetFontInstance() and PhysicalFontCollection::FindFontFamily(). The latter performs several steps, and on my system, it finds OpenSymbol as Symbol's replacement at rFontSubst.getSubstInfo( aSearchName ). There, it searches for exact match of searched name in sorted list. If it wouldn't find OpenSymbol here, e.g. by explicit break for Symbol search, then PhysicalFontCollection::FindFontFamily() will use next method: for symbol fonts, it uses LO configuration org.openoffice.VCL:LocalizedDefaultFonts['lang'].SYMBOL, that is a list of fonts: on my system, it is StarSymbol;OpenSymbol;Arial Unicode MS;StarBats;Zapf Dingbats;WingDings;Symbol. If I add e.g. Standard Symbols L to the head of the list, then "it works".
To fix it properly, I think, two things are necessary:
1. To update OpenSymbol (that is LO native font, and so it must support the necessary glyphs itself, instead of hoping that some system font will happen to have those). I wonder if just copying those glyphs from Standard Symbols L is OK? According to https://en.wikipedia.org/wiki/Ghostscript, the font is either GPL or AFPL.
2. The first step alone if not a proper fix: if user installs a font with a name that will intercept the search in the above-mentioned algorithm, then OpenSymbol won't be selected. So, some hardcoding may be necessary.
Posted a patch to gerrit: https://gerrit.libreoffice.org/28677
I managed to avoid using external fonts as source of absent glyphs, using and modifying OpenSymbol's own glyphs.
Mike Kaganski committed a patch related to this issue.
It has been pushed to "master":
tdf#101889: add absent brackets to OpenSymbol
It will be available in 5.3.0.
The patch should be included in the daily builds available at
http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
Affected users are encouraged to test the fix and report feedback.
@Mike, Khaled *
So, just a thought here--not sure of the feasibility, or the work involved.
Could the scope of OpenSymbol be expanded, its encoding & format adjusted if needed--or a new font spun off to replace it in LibreOffice--that covers more of the Unicode SMP--including the BMP & SMP codepoints for Emoji that we have defined notation for use? And in process maybe expand glyph coverage for musical and mathematics notation.
With so many glyphs enabled now in the GUI we are missing coverage in a project deployed font--could some set of glyphs from Unicode be added to OpenSymbol to cover the glyphs we are defining as Emoji input in the autocorrect tables?
Similar issue in that OpenSymbol is hard coded for use in Math, but misses large chunks of otherwise useful glyphs for formula composition.
Also missing are most of the coverage BMP & SMP for musical symbols. Seems like they all would be well served with a reworked OpenSymbol font.
(In reply to V Stuart Foote from comment #6)
> Could the scope of OpenSymbol be expanded, its encoding & format adjusted if
> needed--or a new font spun off to replace it in LibreOffice--that covers
> more of the Unicode SMP--including the BMP & SMP codepoints for Emoji that
> we have defined notation for use? And in process maybe expand glyph coverage
> for musical and mathematics notation.
IMO, the OpenSymbol is a good place to all that stuff, but... that's a (font) designer's work. If someone volunteers for that, that would be great.
I’d not added any new characters to OpenSymbol unless we really have to, I actually think we should move characters from OpenSymbol (e.g. math, but this require bigger changes in Math) and keep it strictly for bullets and other similar things.
If we really need to bundle and emoji font, we can just use one of the existing freely licensed emoji fonts.
Setting Assignee back to default. Please assign it back to yourself if you're
still working on this issue
** Please read this message in its entirety before responding **
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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!