[Ar-maan05]

the URF default resolution check in ppdCreatePPDFromIPP2() could never match. it compared current_def to a freshly allocated cfNewResolution() so it was comparing pointers, it used resArray[i] insted of [j], and it leaked on every pass. the default always ended up as the middle resolution.

urf-supported RS300-600-1200, printer-resolution-default 1200dpi
before: *DefaultResolution: 600dpi
after:  *DefaultResolution: 600dpi

this first tried to make the loop honor printer-resolution-default, but as Michael pointed out that's about the print engine and not the raster data, so the middle resolution is the better default. now it just uses that and the loop is gone, so the generated PPD doesn't change and only the leak goes away. the comment is updated to match.

added a case to test_ppd_generator that pins the 600dpi result. it passes on top of master with #96.

[michaelrsweet]

Note: "printer-resolution-supported" and "printer-resolution-default" are DIFFERENT from "urf-supported" and "pwg-raster-document-resolution-supported". "printer-resolution" refers to the print engine capabilities, while "urf-supported" and "pwg-raster-document-resolution-supported" refer to the raster processor's capabilities when preparing a source document for printing on the printer. In almost all cases, sending 1200dpi raster data to a 1200dpi printer is a waste of bandwidth since the printer must dither/halftone the source document based on the print engine.

[Ar-maan05]

Thanks, that makes sense, I hadn't thought about the print engine vs the raster data! Sending 1200dpi raster to the printer just to honor that default would be a waste. So I dropped that part: the PPD keeps the middle resolution like it does today, and this now just removes the broken check and the leak that came with it.