On 09/11/10 14:43, Jeremias Maerki wrote: > On 09.11.2010 14:48:30 Vincent Hennebert wrote: >> There may be an interest in fully embedding a font for PostScript >> output. IIUC there may be a print manager that pre-processes PostScript >> files, extracts embedded fonts to store them somewhere and re-use them >> whenever needed. It can then strip the font off subsequent files and >> substantially lighten them, speeding up the printing process. > > It makes the files smaller, but that will be the only thing that > improved printing performance. The PS interpreter still has to parse and > process the actual resource. It also needs to be noted that extracting > subset fonts doesn't make sense. I've already added the unique-ification > prefix to the TTF font names (like in PDF) to avoid problems like that.
That doesn’t solve the problem. AFAIU always the same prefix will be used for the same font. If different FO files are being rendered into PostScript using the same config file, then the PS outputs will all contain the same font name. That may cause serious issues if a post-processing tool concatenates all the files but uses the font instance from the first file only. I think that violates the DSC specification. The only way to ensure uniqueness is to compute some hash sum based on the glyphs used. That may be costly. The alternative is to put the font stream directly in the page stream and not advertise it as a DSC resource. <snip/> Vincent
