The whole ppd / driver stuff is a real mess right now, so I doubt
anything you did would have made it worse!
The mpd file is generated by mkpcdriver. The mpd file is simple a stub
file that then includes the real ppd file. What I was trying to do was
add some standard stuff that could be used across all ppd's. I never
finished it and as you have found it is not always used.
This whole driver thing is next on my list for a big cleanup.
On Sat, 2002-03-09 at 03:31, Adam Crews wrote:
> I was banging my head for a while on this one.
> I have things all working now, but I want to know what I may have
> In the filter script there is a section that checks for ppd files to get
> the options for duplexing and such.
> It looks for <drivername>.mpd and then sets $ppdfile to the path to that
> file if it exists. If not, it looks for <drivername>.ppd and sets
> $stdppdfile to the path to the .ppd file.
> Now, the problem comes when 'getppdstr' is called to get the code for
> duplexing and such. All the places where getppdstr is called, it is
> passed $ppdfile, and not $stdppdfile. As a result, if you don't have
> any mpd's installed, then little things like duplexing, and paper size
> fixing don't work.
> I added a line in the code that sets the $stdppdfile, to also set the
> $ppdfile, and things so far seem to work well.
> So, my question is what is the .mpd file? is this just a modified ppd?
> if so, what's modified about it, if not, where do they come from, and
> why aren't they distributed with ceps?
> Ceps-discuss mailing list
CEPS Team Lead
Desk: +61 2 8446 6344
Mob: +61 418 217 582