On Sun, Jun 15, 2008 at 10:05:59 -0400, Steve Kleene wrote: > I could use some remedial instruction on how Postscript fonts are rendered. > I am submitting a grant proposal to Grants.gov, and the only serifed fonts > they allow are Palatino-Linotype and Georgia. Neither of these is supported > by the typesetter I use, groff 1.18. It does support Palatino, but not > Palatino-Linotype, strictly speaking. By changing the "internalname" in > /usr/share/groff/1.18.1/font/devps/PR (and PB, PI, PBI), I can get the PS > file to list "Palatino-Linotype" everywhere instead of "Palatino". This may > be necessary if they have a really stupid bot checking for font compliance. > > Groff makes the PS, and then I use gs to make a PDF. What I believe is that > people reading this document (likely on Windows) will call up their local > font definitions when they view this. These definitions are used to draw the > characters, but the spacing is all defined by the PDF. Is that correct?
That depends on whether the fonts are embedded in the PDF. You can use the pdffonts command (package poppler-utils or xpdf-utils) to check the PDF that you produce. I would try to make sure that your PDF has all fonts embedded, otherwise the kerning (the inter-character spacing) may be wrong if another font is substituted. This can mean that your file will be rejected if there is some form of visual inspection and it will almost certainly annoy the referees. If your trick with groff results in embedded fonts that are named just like the grants.gov requires it then you should be safe (unless these fonts look very different from the real ones). I would check this with the Adobe reader just to be sure; see File > Properties > Fonts. (Kpdf and evince have the same menus to display the font information but I guess it is most likely that the agency will check with Adobe tools if they check at all.) > I'm less sure how a font is selected for rendering. On Debian, for example, > I use gv to look at the PS file. It presumably uses files in > /usr/share/fonts/type1/gsfonts, but none of these show a FontName that is > Palatino. I can't find where the rule is specified that tells what gsfont to > use for a PS file that lists Palatino. Fonts can be embedded in the PS file, too, so maybe there is no font substitution going on. You can search for "%%DocumentFonts:", "%%DocumentSuppliedResources:", "%%+ font" and "%%BeginResource: font" directives in the postscript code. -- Regards, | http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
