Bugs item #884, was opened at 2007-11-27 09:53 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=884&group_id=106 Category: hz Group: v1.40.5 Status: Open Resolution: Accepted Priority: 3 Submitted By: Robert (schlcht) Assigned to: The Thanh Han (hanthethanh) Summary: Letterspacing and non-autoexpanded fonts Initial Comment: While auto-expanding letterspaced fonts works fine now, there still is a problem with non-automatic expansion. The following will complain about a missing tfm file. It doesn't make a difference whether the expanded font instance is created from an mf file (like below), via `ExtendFont' in the map file, or even whether it was created from a MM font (ie., the expanded instance actually exists as a pfb file). The latter case is what bothers me the most. \pdfadjustspacing2 \pdfmapline{ cmr10} \pdfmapline{+cmr10+100} \font\cmr=cmr10 \cmr \letterspacefont\cmrls=\cmr 100 \pdffontexpand\cmrls 100 0 100 %autoexpand \cmrls Hamburgefonts\par \parfillskip 0pt Hamburgefonts \bye PS: what about the `invalid entry' complaint for the map lines? Are they not legal? ----------------------------------------------------------------------
Comment By: Robert (schlcht) Date: 2007-12-19 16:42
Message: Logged In: YES user_id=2217
A map line needs either a psname (for not-embedded fonts) or the file name (for embedded fonts)
The manual seems to suggest otherwise (re scalable Type 3 fonts). Also, older pdftex versions wouldn't throw a warning, but use the Type 3 font instead. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-11-27 10:05 Message: Logged In: YES user_id=421 A map line needs either a psname (for not-embedded fonts) or the file name (for embedded fonts) ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=884&group_id=106