https://bugzilla.redhat.com/show_bug.cgi?id=2129399
--- Comment #31 from r...@phy.duke.edu --- Well, I read the fonts-conf documentation and examples pretty thoroughly, installed font-manager so I could see the fonts themselves, and there are many, many font sets on the system that contain the requisite characters. It is very difficult to tell which one is causing the problem or how to replace it. I spent two hours trying variations on your <alias> section including <match> statements, replacing the various systems fond initialization steps, etc. It sadly remains the case that while I can display my unembedded test file on a scientific linux box in the department and it renders perfectly (over X) when I try to look at exactly the same file on Fedora it has nothing but boxes. My embedded font ps2pdf version of the same file displays everywhere. I agree that it is probably something in /etc/fonts/fonts.conf and/or /etc/fonts/conf.d/[??]whatever-symbol-font-isn't-working.conf and that just the right override might fix it, that requires diffing and checking around 100+ files, most of which are certainly irrelevant, looking for a possibly significant change in an XML that I don't completely understand to see which one works correctly on scientific linux (a RH base IIRC) but not on Fedora (another RH base). I could maybe install a Centos VM to test -- I don't have a RH license on any personal systems, obviously. The possibility remains that it is a change in evince itself as well. This I can't really test -- obviously, if I copy over a binary from the system where it works it has the wrong libraries on my laptop, and mucking around at the library level is an open invitation to having to do a hard reinstall (been there, done that:-). Right now I HAVE to go back to my regular work and write a quiz for my physics students with (sigh) embedded fonts and so far I nothing I've done has fundamentally broken font rendering per se, but in any event no, the alias above does not work whether or not it is font.conf or 0-symbol.conf. The documentation suggests that the former is the right place for it -- and I could verify that this file was indeed being parsed in real time as I made changes as errors were instantly reported in tty's containing rendered fonts -- but the latter seems like it might only be scanned at boot or login time, since the leading 00 (if I understand things) represents the order in which the file configs are layered at startup. I >>think<< the system rereads this ever 30 seconds by default so it shouldn't matter, but again -- no time to test, an incredibly complex system and syntax, and crappy tools for manipulating it or even displaying it. Font-manager is the best I've found, but I don't know if it can be used to rewrite rules yet (or if it is wise to trust it while doing so). Sorry. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2129399 _______________________________________________ fonts-bugs mailing list -- fonts-bugs@lists.fedoraproject.org To unsubscribe send an email to fonts-bugs-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/fonts-bugs@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
