On Tue, 13 Jul 2021 14:12:47 -0400 Edward <epp(a)caramail.com> wrote: Helvetica isn't a Microsoft font. It's a sans-serif commonly seen on Macs. The usual Microsoft replacement is Arial, but I don't think it's 100% metrically identical, so Liberation Sans wouldn't be either. Of course, it's possible that the Helvetica fonts aren't actually used anywhere in the document and that the two nameless fonts are derivatives of something else altogether. That would be far from the stupidest thing I've ever seen anyone do with a PDF file. That suggests a kerning problem, and possibly an unsuitable font substitution. You may want to dig into your distro's information on fontconfig. The command "fc-match Helvetica" can be used to see what your system's substitute for Helvetica is. It's also possible the designer was a bonehead and adjusted the spacing between letters without embedding the font. That's . . . a little more difficult to fix. E. Liddell

Anno domini 2021 Tue, 13 Jul 17:21:44 -0400 Edward scripsit: Devuan chimaera: $ fc-match Helvetica NimbusSans-Regular.otf: "Nimbus Sans" "Regular" Oh, and then there is that ugly Helvetica-replaced-by-blocky-font problem with firefox when you install xfonts package ... nik -- Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ...

On 7/14/21 5:12 PM, E. Liddell wrote: I tried this in LibreOffice Writer. Default font was Liberation Serif, which looked similar to Times New Roman. Changing this text to the TeX Gyre Heros font, changed it and the result looked like Helvetica. Although I will admit that I discovered an unusually large quantity of Noto fonts that are all foreign language characters, This caused the font list to hang in LibreOffice, so I have uninstalled those packages, it freed up over 600Mb on the hard drive. -- Linux. A Continual Learning Experience. TDE: R14.0.10 - Debian: 10.10 (amd64)

On Tuesday 13 July 2021 01:16:12 pm Dr. Nikolaus Klepp wrote: Or probably just drag and drop the file into a Chromium tab? That works with most browsers, but someone with Chromium installed would need to test it...

Ah OK, didn't know this is what you meant :) Gianluca ----------------------------------------------------- Gianluca Interlandi, PhD gianluca(a)u.washington.edu +1 (206) 685 4435 http://gianluca.today/ Department of Bioengineering University of Washington, Seattle WA U.S.A. -----------------------------------------------------

On Wed, 14 Jul 2021, Steven D'Aprano via tde-users wrote: I thought this is true only if the fonts are embedded in the PDF. It has happened to me in the past that a PDF would not render and print correctly until I had installed the MS TrueType fonts. Gianluca ----------------------------------------------------- Gianluca Interlandi, PhD gianluca(a)u.washington.edu +1 (206) 685 4435 http://gianluca.today/ Department of Bioengineering University of Washington, Seattle WA U.S.A. -----------------------------------------------------

On Sat, 17 Jul 2021 01:06:51 +1000 "Steven D'Aprano via tde-users" <users(a)trinitydesktop.org> wrote: There's a whole bunch of messy intellectual property problems with that. Most people don't bother to investigate who their fonts belong to or what redistribution rights they have, and Windows and Mac OSX (both the OSs themselves and common software for them) ship with a lot of "all rights reserved" fonts, some of which may be legacy fonts without formal "no embedding" markers. So no, embedding fonts by default unfortunately would make a lot of people criminals, technically speaking. E. Liddell

On Fri, Jul 16, 2021 at 12:14:26PM -0400, E. Liddell wrote: [...] Not really. Its quite simple: if the font has the "Allow embedding" flag turned on, embed it. Done. Some Adobe products -- but not all -- already ship with font embedding enabled by default. Of course they honour the embedding permissions, but you don't have to enable a setting for them to embed the fonts you use if they allow embedding. They just go ahead and do it, even if you turn off embedding. Quote: "... most but not all of the .joboptions file font embedding options are totally and utterly ignored. The options that are ignored are the Embed all fonts, Embed OpenType fonts, Always embed, and Never embed." https://community.adobe.com/t5/indesign/fully-embedding-fonts-in-pdf/m-p/66… The details are quite complex -- font embedding only embeds the glyphs, not the whole font, they may embed the special fourteen fonts that all postscript printers support, which most programs don't do, there are special rules for fonts used in editable text fields, blah blah blah. But for an application like LibreOffice, for example, all that we need is for the checkbox Archive PDF/A-1a (ISO 19005-1) to default to ON instead of OFF. There's no good reason for it to default to OFF. That's equivalent to "Embed fonts (if permitted)". It's not up to the user to check the permission bits, the PDF creator software should do that. (And ideally pop up a notice that "font X is used but cannot be embedded".) Unless you are referring to ancient bitmap fonts from the Dark Ages, I doubt that is even possible to have fonts without embedding permissions. And such ancient bitmap fonts can't be embedded. OpenType fonts have *always* required such permissions, since the day the standard was invented. I think the same applies for TrueType fonts, they certainly have them now, and I'm quite sure (but haven't found a definitive source) that they too have always supported them. https://www.microsoft.com/en-us/microsoft-365/blog/2015/07/06/document-font… (Similarly for Postscript Type 1 and 3 fonts.) But in either case, it doesn't really matter so long as the software follows a "default deny" approach: lack of permission flags is equivalent to forbidding embedding. That's wrong: only fonts that explicitly permit embedding would be embedded. But even if it were correct (say you use an application that fails to honour the embedding permission flags, or uses a "default allow" system), your argument is FUD (Fear, Uncertainty, Doubt). Yes, embedding fonts in your PDF *might* make you a criminal. And forwarding an email (without or without attachments) *might* do the same. Nevertheless most mail clients default to quoting on reply and copying attachements when forwarding. Either of which *might* make you a criminal! But it almost certainly won't. Let's be real here: you're talking about a scenario where: - the PDF creator software foolishly treats missing permissions as "allow" rather than "deny"; - the legacy fonts embedded are a format that doesn't include embedding permissions; - their retail value is above $1000 (the threshhold in the USA for copyright infringement to be a criminal felony); - the copyright holder of the legacy font still exists; - and finds out you have embedded the fonts; - and gives a shit about it; - and aren't satisfied with just ordering you to cease and desist distribution; - and persuade the legal authorities to care; - and the authorities actually bother to press charges. I don't think I'm going to lose sleep over that. -- Steve

On 7/20/21 4:14 PM, Edward wrote: With installing Adobe Acrobat Reader on my Android, this was confirmed while viewing the same PDF. -- Linux. A Continual Learning Experience. TDE: R14.0.10 - Debian: 10.10 (amd64)

On 7/23/21 6:05 PM, Michael via tde-users wrote: When I looked at the font info for the PDF in question, it was all-Helvetica, which would explain why what would have been the MICR line at the bottom, printed in a completely different font. It's likely due to the way the PDF was created. I looked at another PDF that also has a MICR line at the bottom and that PDF displayed as expected. I guess I probably didn't need to install the GnuMICR font in the first place, as it didn't actually solve the problem with the first PDF. -- Linux. A Continual Learning Experience. TDE: R14.0.10 - Debian: 10.10 (amd64)