[NTG-pdftex] open problems with 1.20a
Fri, 9 Jul 2004 01:53:10 +0200 (CEST)
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
Content-Type: TEXT/PLAIN; charset=iso-8859-1
On Thu, 8 Jul 2004, Martin Schr=F6der wrote:
> Could someone (Hartmut?) please elaborate a bit on these items:
> - support embedding base fonts.
> - fixed a few problems with handling fonts in included pdf.
> - support for auto font expansion -- expanded TFM's are not
> - support for base font inclusion as suggested by Hartmut
- support for standard font embedding
The 14 Type 1 "standard fonts" (Times, Helvetica...) are now more or
less handled like any other Type 1 font. The embedding of these standard
fonts is not any more blocked, if their true FontName is given as the
2nd field in a pdftex.map line. If a FontName out of the standard fonts
is listed there, but the corresponding font file can't be found, a
warning will be issued, and an unembedded version of the standard font
will be used. It's then up to the PDF viewer application to display the
text by its own standard font version.
If a font with FontName _not_ belonging to the "standard fonts" is given
in pdftex.map, and the corresponding font file can't be found, a warning
will be issued, and the font will be replaced by some default font
(which will normally be visually distracting).
Checks of fontfile existence will be done at the time when the font is
- support embedded standard fonts in included PDF files
When a PDF file with embedded fonts is to be included, its FontName
entries will be matched against the FontName fields (2nd field) in the
pdftex.map file. If a match is found, the embedded font will be replaced
by a font managed by pdftex. This normally reduces the PDF file size,
when several included PDF files contain glyphs from the same font. The
font replacement works now also for Type 1 standard fonts embedded into
the included PDF files. If the pdftex.map file contains more than one
line with the same matching FontName field, the best suited replacement
font will be selected, using hierarchical criteria of whether a font is
already in use (best case), or whether the TFM file is existing or not.
Unembedded fonts coming with included PDF files are generally left
- fixed a few problems with handling fonts in included pdf.
- support for auto font expansion -- expanded TFM's are not required
Needs some example runs to see how it now works. Also what's now with
these obsolete expanded font files like font+15.tfm or MM instances like
font-30.pfb: Do they hurt? Can they still be used? All this is cleaned