<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Mar 3, 2009, at 2:23 PM, Smith Kennedy wrote:</div><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div><div><div>On Mar 3, 2009, at 12:08 PM, Michael Sweet wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Mar 3, 2009, at 7:49 AM, Smith Kennedy wrote:</div><blockquote type="cite"><div><font class="Apple-style-span" color="#000000">...<br></font>If this is expected behavior (I seem to recall finding in my thrashing that it is), </div></blockquote><div><br></div>It is currently the expected behavior; optimizing the output is on our TODO list but hasn't yet happened.</div></div></blockquote><div><br></div>My mistake - I thought it used to do this some time ago, but I must have been mistaken. Will this be in the DDK included with CUPS 1.4?</div></div></div></div></blockquote><div><br></div>Probably not in 1.4.0, but likely for a later 1.4.x update.</div><div><br><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div><div><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><blockquote type="cite"><div>...</div></blockquote></div></div></blockquote></div></div></div></div></blockquote><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div><div><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><blockquote type="cite"><div>I thought the problem might be that the files were not "normalized", so tried importing one using ppdi and then re-generating it using ppdc, and did the same thing for the second one. Interestingly, ppdi refused to import the ppds generated by ppdc.<br></div></blockquote><div><br></div>What errors did you see?</div></div></blockquote><div><br></div><div>There were no errors written out to stdout or stderr. Here is an example run I did just now:</div><div>...</div></div></div></div></div></blockquote><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div><div><div><span class="Apple-style-span" style="color: rgb(0, 0, 0); ">Notice that there were no error messages written out by ppdi when importing hp1300_6.ppd. But the "new.drv" file doesn't have the LaserJet 1300 in it. I checked system.log and the console log in Console.app on Mac OS X and didn't see anything.</span></div></div></div></div></div></blockquote><div><br></div>Can you re-test with the current CUPS 1.4 release or Subversion sources?</div><div><br></div><div>I'll see about adding a unit test for this to the standard build.</div><div><br><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div><div>...</div></div></div></div></blockquote><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div><div>Hand-editing is tricky, which is why I was hoping to use the tool. :-)</div><div><br></div><div>Perhaps a 1-level pass would be possible as a first-phase enhancement that could make it into 1.4, with multi-level implemented later?</div></div></div></div></blockquote><div><br></div>That's the most likely path, although like I said it might not show up until 1.4.x</div><div>(x > 0)</div><div><br></div><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Monaco; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>________________________________________</div><div>Michael R Sweet, Senior Printing System Engineer</div></div></div></span></span>
</div>
<br></body></html>