Note: please don't spam any of the e-mail addresses which you see here. Follow this link if you want some addresses to misuse.
From: David Chappell <David.Chappell@mail.cc.trincoll.edu> Date: 18 Apr 2002 20:39:16 -0400 Subject: PPR: CIDInit On Wed, 2002-03-27 at 18:49, Dr Douglas J. Chappell wrote: > >difficulties printing PDF's from Windows 2000 as well. For the PDFs that > >don't print ppr states that the procset resource CIDINIT is not found, but it > >appears to be there when looking at the ps file. any help would be greatly > >appreciated. > > Something like this? > # ppop log sc2-1234 > : > : > +Job turned away from printer "sc2p2" for the following reason(s): > +Resource "ProcSet CIDInit" not available. > > > We are having similar problems here, however, the procset is not present. > Are you sure you have the CIDInit procedure set? The postscript in the job > files I have looked at defines only that CIDInit is needed. > > %%DocumentNeededResources: procset CIDInit > %%IncludeResource: procset CIDInit > What I'd like to be do is to install these procsets in the cache > (/usr/share/ppr/cache/procset) and have ppr add them on the fly. I note that > the latest ghostscript seems to have CID font support. I don't know if I have answered this question yet. The "%%IncludeResource: procset CIDInit" comment basically asks PPR to include the procedure set unless it knows that the printer already has it. I haven't figured out where one gets CIDInit, but I found that our printer had the procedure set on its hard disk. To temporarily fix the problem I did this: $ touch /usr/share/ppr/cache/procset/CIDInit-0-0 That gives PPR an empty file to 'send'. This keeps PPR happy and since the printer has the procedure set already, it doesn't matter that the file is empty. In the CVS code, I have made a change that assumes that Level 3 printers have CIDInit. Does anyone know if this is correct? How does one figure out (from the PPD file) if a printer has CIDInit?