Time for Type3 bitmap fonts to cause a warning?
Type3 bitmap fonts look much worse on most output devices than properly-hinted Type1 fonts. Type3 fonts also can cause problems with PDF interpreters in printers, which sometimes no longer implement all aspects of the Type3 language correctly. Type3 fonts were once a hack that seems no longer widely used outside the TeX community, and therefore are now less well tested and supported by device manufacturers. Type3 bitmap fonts seem an anachronism from the 1980s, when it was customary to output DVI files using Metafont-generated device-specific bitmaps, and when there were only a small number of standard output resolutions in use. Today, I find that in nearly all cases where I encounter pdftex-generated documents with Type3 bitmap fonts, these were actually selected by an inexperienced author by accident, (often as a result of copying a line such as \usepackage[T1]{fontenc} without understanding its font-selection implications). Suggestion: it would be useful to actively discourage in pdftex the use of Type3 fonts. This could be done in steps, e.g.: - initially just output a warning that prominently lists any Type3 fonts used in the PDF produced (plus add an "I know what I do and really want Type3" command-line override option to suppress that warning) - later turn that warning into an error, such that Type3 fonts can now only be included into PDFs using the "I know what I do and really want Type3" command-line option, to make sure they only appear in PDFs as a deliberate choice by an experienced author. [The idea is similar to how HTTPS browsers like Chrome or Firefox gradually added warnings to phase out outdated cryptography.] If Type3 fonts generated a clear warning, this would make it much easier for the authors of document-submission guidelines to tell PDF authors what they need to avoid. At the moment, such guidelines have to rely on more complex instructions to check font types with e.g. pdffonts file.pdf | grep 'Type 3' Markus -- Markus Kuhn, Computer Laboratory, University of Cambridge http://www.cl.cam.ac.uk/~mgk25/ || CB3 0FD, Great Britain
Subject: [NTG-pdftex] Time for Type3 bitmap fonts to cause a warning? I see your argument, but (in any case) this is not something I am prepared to do for the upcoming TeX Live 2017. I'll think about it more after the release. Thanks. -k
On 2017-03-28 at 12:50:10 +0100, Markus Kuhn wrote:
Suggestion: it would be useful to actively discourage in pdftex the use of Type3 fonts.
This could be done in steps, e.g.:
- initially just output a warning that prominently lists any Type3 fonts used in the PDF produced (plus add an "I know what I do and really want Type3" command-line override option to suppress that warning)
- later turn that warning into an error, such that Type3 fonts can now only be included into PDFs using the "I know what I do and really want Type3" command-line option, to make sure they only appear in PDFs as a deliberate choice by an experienced author.
[The idea is similar to how HTTPS browsers like Chrome or Firefox gradually added warnings to phase out outdated cryptography.]
Dear Markus, I understand your point. But nowadays TeX Live is configured to use outline fonts by default. If people use bitmap fonts they do it either deliberately (and a warning or error message isn't helpful) or something else went wrong. In the latter case more explanation is needed because presumably many users don't know how to proceed. What I can imagine is that whenever a bitmap font is used, a message is issued which points users to a file which provides more information (accessible with texdoc). BTW, the problem we're talking about affects other engines as well. Regards, Reinhard -- ------------------------------------------------------------------ Reinhard Kotucha Phone: +49-511-3373112 Marschnerstr. 25 D-30167 Hannover mailto:reinhard.kotucha@web.de ------------------------------------------------------------------
participants (3)
-
Karl Berry
-
Markus Kuhn
-
Reinhard Kotucha