PDF viewer messing up fonts in web view, potentially more (aditionals unconfirmed, i.e. printer))
idk, what i did, but i assume it's most likely user error. but i don't even know where to go from where i'm at.
ok, i'm going to attempt to identify what is happening. [guess] .pdf website previews are messing up the font when converting the .pdf to an image asset for the website to use as a current web asset, when the .pdf is updated. (makes sense really, smart drag & drop update of a .pdf menu, has instruction to make the end users browser do the work for you. kind of a one and done webpage coding for older guys that can't type, let alone edit Html, or even use Wix. some people just don't "compute" hard R or not. lol )
i don't even know where to start. i mean Mozilla is probably referencing it's own "lib.moz" which is just probably it's own personal link to an existing Lib file so it can pull it in and do what it needs to do with it without Root etc.
that is probably working fine as it renders (opens) the .pdf fine whence it's downloaded it. so all that i've talked about might not be the problem.
there is probably some mozilla function calling that to convert the .pdf as an image web asset so that it can show a preview of the current .pdf available for download.
that converter is messing up the font recognition, and building a preview image with messed up font characters (why it looks like Wing-Dings). but i don't even know where to start, and i don't think a new install will solve this (kinda overkill, and any residual files may still remain.)
i'm adding a fastfetch
───────────────────────────────────────────────────────────────────── BIOS (UEFI) F20 (4.6) Board X79-UD3 (1.1) ───────────────────────────────────────────────────────────────────── CPU Intel(R) Core(TM) i7-3820 (8) @ 3.80 GHz CPU Cache (L1) 4x32.00 KiB (D), 4x32.00 KiB (I) CPU Cache (L2) 4x256.00 KiB (U) CPU Cache (L3) 10.00 MiB (U) ───────────────────────────────────────────────────────────────────── GPU NVIDIA GeForce GTX 1660 SUPER [Discrete] Vulkan 1.4.341 - NVIDIA [610.43.02] OpenCL 3.0 CUDA 13.3.44 OpenGL 4.6.0 NVIDIA 610.43.02 ───────────────────────────────────────────────────────────────────── Display (VG248) 1920x1080 @ 1.5x in 24", 60 Hz [External] * Display (VG248) 1920x1080 @ 1.5x in 24", 60 Hz [External] Display (TOSHIBA-TV) 1920x1080 @ 1.5x in 72", 60 Hz [External] ───────────────────────────────────────────────────────────────────── Memory 9.66 GiB / 31.26 GiB (31%) Swap 12.00 KiB / 1.91 GiB (0%) Disk (/) 675.49 GiB / 7.22 TiB (9%) - ext4 ───────────────────────────────────────────────────────────────────── OS Linux Mint 22.3 x86_64 OS Age 99 days Uptime 5 days, 2 hours, 40 mins Packages 2452 (dpkg), 18 (flatpak) ───────────────────────────────────────────────────────────────────── Kernel Linux 6.17.0-35-generic Bootmgr Ubuntu - shimx64.efi gcc 13.3.0 Init System systemd 255.4-1ubuntu8.16 Shell bash 5.2.21 LM lightdm-autologin 1.30.0 (X11) DE Cinnamon 6.6.7 WM Muffin (X11) Terminal GNOME Terminal 3.52.0 Terminal Font MesloLGS Nerd Font Mono (12pt) ─────────────────────────────────────────────────────────────────────
Mozilla Firefox 152.0.1 " updates are manage by your operating system."
re-posted from; [[Why is Firefox PDF printing so strange?|https://support.mozilla.org/en-US/questions/1275786#answer-1276068]]
and edited: reasons; support ticket gudelines
[[Posting support requests|https://support.mozilla.org/en-US/kb/mozilla-support-rules-guidelines#w_subjects-covered-in-the-support-forum]]
[[i somewhat found an "answer" though i'd hardly call that "solved."|https://support.mozilla.org/en-US/questions/1275786#answer-1276068]]
i still say a Lib in a repo needs updated, within, or perhaps up stream of the project to reflect "commonly used fonts" if applicable (i know that's the trick, 'is it FOSS') yet other browsers use it, though idk if they're FOSS... i'd need to know what i'm looking for to confirm that or not, and do something about that (again most likely upstream, as the PDF Viewer is probably it's own project (or even several), retooled by Mozilla for Firefox.
All Replies (1)
Could you explain a bit where Firefox enters the equation here? I don't assume you're using the builtin PDF editor functionality to make changes to the existing PDF for website publishing — so you're probably making these edits in some authoring software… and the results of that PDF output are then being corrupted when the CMS–like system distills that into preview images — which it doesn't use Firefox for.
So it sounds like a compatibility wrinkle between the PDF authoring results/settings, and the CMS conversion inputs?
You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.