All of lore.kernel.org
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmail.com>
To: Michael Sweet <msweet@apple.com>
Cc: "printing-architecture@lists.linux-foundation.org"
	<Printing-architecture@lists.linux-foundation.org>
Subject: Re: [Printing-architecture] CUPS queues should emulate IPP Everywhere printers - First tests
Date: Fri, 08 May 2015 18:47:34 -0300	[thread overview]
Message-ID: <554D2EF6.6030906@gmail.com> (raw)
In-Reply-To: <0E9CA9DC-A99D-485D-9FFF-EA0EA09FBDA3@apple.com>

On 05/08/2015 04:03 PM, Michael Sweet wrote:
> Till,
>
>> On May 7, 2015, at 6:56 PM, Till Kamppeter <till.kamppeter@gmail.com> wrote:
>> ...
>> 1. Many FAILs. Where should I report them? CUPS bugs? CUPS mailing list? This mailing list?
>
> Problems with CUPS should be filed as CUPS bugs.

Filed https://www.cups.org/str.php?U4630

Note that I had problems to attach the plist files. Can you make your 
bug system accepting them directly (files with spaces in name, *.plist 
files, data format)? I succeeded only by putting them into a tarball.

>
>> 2. The IPP test prints a JPG file. Isit required for an IPP Everywhere printer to print JPG? Is not PWG Raster the only required format?
>
> Both JPEG and PWG Raster are required.
>

OK, so I will make the System V interface for PPD-less 
cups-browsed-auto-generated queues also accept JPG.

>> 3. The JPG file printed by the IPP test consumes a lot of ink. Can one not use a text page converted to JPG for this test?
>
> No.  The purpose of JPEG file printing is photo printing, so we need to validate the output quality.  Text-as-JPEG would not adequately test things.
>

So then the IPP test which is not about whether photos come out 
correctly but whether jobs are sent, correctly listed, and removed from 
list when donw shoot use documents in PWG Raster format as example 
files. Can be very low resolution for this test,

>> P. S.: CUPS 2.0.2 has no everywhere directory, does this only appear in 2.1.x?
>
> The source tarballs don't have the "everywhere" directory, you need to get them from the Git repository...
>

OK.

> But like I said at the PWG meeting, you need to use the tools posted on the PWG web site; what is in the CUPS repository is for development of the tools only.
>

I have the scripts from these PWG packages. I only wanted to know of 
their upstream home.

    Till


  reply	other threads:[~2015-05-08 21:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-07 22:56 [Printing-architecture] CUPS queues should emulate IPP Everywhere printers - First tests Till Kamppeter
2015-05-08 15:17 ` Ira McDonald
2015-05-08 19:03 ` Michael Sweet
2015-05-08 21:47   ` Till Kamppeter [this message]
2015-05-10 18:09     ` Michael Sweet

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=554D2EF6.6030906@gmail.com \
    --to=till.kamppeter@gmail.com \
    --cc=Printing-architecture@lists.linux-foundation.org \
    --cc=msweet@apple.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.