Created attachment 1881507 [details] A zipped sample PDF and image of relevant portion of PDF when affected by the issue Description of problem: Given a PDF lacking embedded fonts which use certain characters (including → and ≥), GNOME's Evince on Fedora 36 chooses to substitute the Noto Sans font, which does not include these characters. Version-Release number of selected component (if applicable): How reproducible: Successfully reproduced by two people independently. Steps to Reproduce: 1. Boot a fresh copy of Fedora 36 (the Live version in a VM will do). 2. Open the attached sample PDF in GNOME Evince (aka Document Viewer). 3. Observe the missing characters in the second paragraph from the top of the page. Actual results: See attached image. Expected results: The missing characters should be displayed properly as → (that is, https://unicode-table.com/en/2192/). Additional info: The filer initially sought help at https://ask.fedoraproject.org/t/missing-characters-in-pdfs-since-upgrade-from-f35-to-f36/22530, which may be informative in reproducing the issue.
Created attachment 1881508 [details] A sample PDF which may be used to reproduce the issue
Created attachment 1881509 [details] An image demonstrating the appearance of the PDF when the issue is reproduced
Comment on attachment 1881507 [details] A zipped sample PDF and image of relevant portion of PDF when affected by the issue When I went to file this issue it seemed I could only upload a single attachment. After filing I discovered I could add more, and added the files directly for easier access. This attachment may be deleted if desired.
FEDORA-2022-a3bf4d3246 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2022-a3bf4d3246
FEDORA-2022-a3bf4d3246 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-575472271c has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-575472271c
FEDORA-2022-575472271c has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-575472271c` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-575472271c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-575472271c has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
I am a different user still experiencing these exact issues! I think the bug should be reopened. I downloaded the sample files and still experience the same exact problem, namely that certain special characters are missing, and displayed as boxes, in evince, but not with other software (i.e. the same PDF opened in Firefox displays all characters correctly). I am using Fedora 37 fully updated, in fact the same issue is present in 3 different machines with the same system, and I've had this issue for a while just like the original poster, since upgrading to Fedora 36. I regularly experience this issue with PDFs that I create using R (plots containing innocuous symbols such as a minus sign and greek letters), which interferes with me giving presentations! This bug is a big deal to me professionally, and at least having a workaround would be greatly appreciated. Here's what `pdffonts` reports on a recently offending file I created, which matches the original bug report in showing a "Symbol" font that appears the be the source of these problems: $ pdffonts pq-tgp-delta-boxplot.pdf name type encoding emb sub uni object ID ------------------------------------ ----------------- ---------------- --- --- --- --------- Helvetica Type 1 Custom no no no 10 0 Helvetica-Bold Type 1 Custom no no no 11 0 Symbol Type 1 Symbol no no no 12 0
I just checked, and the issue is still occurring for me on my main Fedora 37 install. I will try to reproduce in a clean VM later this week.
I just tried several PDF files with maths symbols in them on an up to date FC37 machine and an up to date FC38 machine. They display just fine when opened with Firefox, but the symbols still don't display with Okular or evince. fc-match Symbol (the font these PDF files are using) gives 'StandardSymbolsPS.t1: "Standard Symbols PS" "Regular"'. It seems like this is an obsolete configuration.
Okay, this seems to happen that urw-base35-standard-symbols-ps-fonts has a substitution rule with strong binding instead of weak binding. this is why they still have higher priority than google-noto-sans-symbols-fonts. I'll take another change in google-noto-fonts.
FEDORA-2023-ad30c3e882 has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2023-ad30c3e882
FEDORA-2023-db296088a5 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-db296088a5
FEDORA-2023-aa001fcfe5 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-aa001fcfe5
FEDORA-2023-8b6bc9ef2f has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-8b6bc9ef2f
FEDORA-2023-ad30c3e882 has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.
I just tried the new font RPMs that are in testing. Now a proper "Symbol" font is being chosen for symbols, and I see a lot more of them in PDFs displayed using evince or okular. However, the fonts being used - NotoSansSymbols and NotoSansSymbols2 - seem to be missing a number of symbols needed for technical documents. For example, the symbols for set expressions, like "U+2286 SUBSET OF OR EQUAL TO", do not appear to be in these fonts. So, my documents still display with a lot of problems using evince or okular. They display correctly in Firefox.
FEDORA-2023-db296088a5 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-db296088a5` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-db296088a5 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-aa001fcfe5 has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-aa001fcfe5` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-aa001fcfe5 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-8b6bc9ef2f has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-8b6bc9ef2f` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-8b6bc9ef2f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-aa001fcfe5 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-db296088a5 has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-8b6bc9ef2f has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
I may be wrong but I think this bug - or something very similar - is persisting. According to the Evince -> preferences -> fonts, the Symbol font is being substituted with Noto Sans. I think this font doesn't have all the required glyphs. @alexviiiag for a work-around, make a .font.conf file in ~/ with the following: <?xml version="1.0"?> <!DOCTYPE fontconfig SYSTEM "fonts.dtd"> <fontconfig> <match target="pattern"> <test name="family" qual="any" > <string>Symbol</string> </test> <edit name="family" mode="assign" binding="same"> <string>OpenSymbol</string> </edit> </match> </fontconfig> OpenSymbol will need to be installed for this to work: It's in libreoffice-opensymbol-fonts if you need to install it. From the name I'm guessing it comes with libreoffice so maybe we already have it? Otherwise you can embed the fonts yourself with ghostcript (sudo dnf install ghostscript if you don't have it), with the command: gs -dNOPAUSE -dBATCH -dPDFSETTINGS=/prepress -sDEVICE=pdfwrite -dEmbedAllFonts=true -sOutputFile=insert_output_file_name_here.pdf -f insert_input_file_name_here.pdf But it would be good if this could be fixed system-wide at some further upstream point. I don't have the knowledge to say where and how. Thanks in advance
This change has been reverted because of Bug#2129399 Please open another issue against libreoffice-opensymbol-fonts to have a substitution for Symbol or keep discussions at Bug#2129399.