Glen,
I was more thinking "where to put it in the header", but I've since decided to put PrintQuality in one of the empty cupsInteger slots and put your PrintContentType in the OutputType string field.
Ira,
As for which specification, since the first use is in the PWG Raster Format spec, I'm thinking we should put it in the PWG Raster Format spec and then include it in the list of required IPP Everywhere job template attributes...
Thoughts?
On Sep 12, 2011, at 3:53 PM, Petrie, Glen wrote:
>>>> New Attribute
>> PrintContentType: Text, Text+Graphics, Graphics(vector), Photo
>> This is combined with “OutputType” to optimize output.
>> This was big discussion in JTAPI definition and it was determine that is necessary to have both values.
>> We don't have this in the semantic model or IPP yet. Where do you propose I put this?
>> I am not sure what you mean “where do you propose I put this”?
>> If you mean --
> Within the PWG Raster it can occupy the first; no, better yet the last 4 bytes of the vender data space and shorten the vendor data space.
>> If you mean--
> Where will the information come from in a SM or IPP “job ticket”; then, I agree there is no source. But if an application choices to create a PWG Raster file and knows the PrintContentType value; then the application can fill in the field. The default value of zero (‘0’) can represent the value of “unknown” or “not specified”. So the enum could be
>> typedef enum {
> NotSpecifed = 0,
> TextOnly,
> TextAndGraphics,
> GraphicsOnly,
> Photo
> } ContentTypeEnum
>>>>>> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean. _______________________________________________
> ipp mailing list
>ipp at pwg.org>https://www.pwg.org/mailman/listinfo/ipp
__________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20110918/e3adca08/attachment-0001.html>