In bug 93968, the issue was resolved for LO's default symbol font, OpenSymbol, but the same also needs to happen for other symbol fonts like Webdings, Wingdings, Wingdings 2, and Wingdings 3. Caolan suggested in bug 93968 comment 13 to expand the available list of symbol fonts in svtools/source/misc/sampletext.cxx under isSymbolFont[1] and then the necessary coding can use that as the basis for the fix. Heiko, Stuart, Cor: Do you know any symbol fonts on Windows or Linux that should be added to the list? Alex, Steve: Do you know any symbol fonts on Mac that should be added to the list? Caolan: Maybe you can provide a bit more details on how this can be achieved so maybe it could be an easy hack. ;D ---- [1] https://cgit.freedesktop.org/libreoffice/core/tree/svtools/source/misc/sampletext.cxx#n106
Not an expert in this field but maybe Akshay. Arch Wiki talks about ttf-symbola https://wiki.archlinux.org/index.php/Fonts#Emoji_and_symbols, and Braille font might be interesting too.
Seems the previews in the font name combobox seems to already have the necessary code to not render such fonts and it would be useful for both locations to share this same. (In reply to Heiko Tietze from comment #1) > Not an expert in this field but maybe Akshay. Arch Wiki talks about > ttf-symbola https://wiki.archlinux.org/index.php/Fonts#Emoji_and_symbols, > and Braille font might be interesting too. Checked symbola and the emoji fonts and they were fine, but Braille wasnt (bug 108738). This is the list of symbol fonts on my system that didnt render correctly. Webdings Wingdings Wingdings 2 Wingdings 3 Bookshelf Symbol 7 So here is the patch - https://gerrit.libreoffice.org/39217
Yousuf Philips committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=3e82c30b89b87199b8f20658beecbfccccffcd52 tdf#108720 Add symbol fonts to isSymbolFont() It will be available in 6.0.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: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
include/svtools/sampletext.hxx isSymbolFont currently takes a const vcl::Font &rFont and checks its charset and its family name, so I suggest changing isSymbolFont to take a rtl_TextEncoding eCharSet and OUString familyname argument instead. Then where we currently pass in rFont to pass in rFont.GetCharSet(), rFont.GetFamilyName() and in svx/source/styles/CommonStylePreviewRenderer.cxx where we now have if (IsStarSymbol(pFontItem->GetFamilyName())) change that to if (isSymbolFont(pFontItem->GetCharSet(), pFontItem->GetFamilyName()) and presumably that should then do the right thing
Gulsah, Aron: Maybe one for the weekend. ;D
On a fairly default OSX installation : Bodoni Ornaments Stix (seems to be maths sysmbols) Symbol Webdings Wingdings Wingdings2 Wingdings3 Zapf Dingbats Apple Braille Apple Color Emoji
** 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! Warm Regards, QA Team MassPing-UntouchedBug
Everyone, please open follow-up bugs for individual font requests. Mark those as blocking this bug.
Caolán outlined a suggestion with code pointers in comment 4 that as far as I can see hasn't been implemented, perhaps let's leave this bug report open until that is done.
Dear Yousuf Philips (jay) (retired), 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! Warm Regards, QA Team MassPing-UntouchedBug
Dear Yousuf Philips (jay) (retired), 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 https://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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Seems to still be an issue, suggested refactoring of comment 4 remains to be done. Meanwhile os/DE specific PUA only symbol fonts, e.g. "HoloLens MDL2 Assets" and "Segoe MDL2 Assets" from Windows 10, have to be dealt with.
as in comment 12, refactoring suggested comment 4 not yet in place. @Khaled, any interest?
*** Bug 93286 has been marked as a duplicate of this bug. ***
It should be an easy hack