All of lore.kernel.org
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmail.com>
To: Klaus Singvogel <kssingvo@suse.de>,
	printing-architecture@lists.linux-foundation.org,
	printing-foomatic@lists.linux-foundation.org,
	Tim Waugh <twaugh@redhat.com>, David Suffield <suffield@hp.com>,
	shiyun.yie@hp.com,
	gimp-print-devel <gimp-print-devel@lists.sourceforge.net>,
	Printing-japan <printing-japan@lists.linux-foundation.org>
Subject: Re: [Printing-architecture] Printer setup tools: Automatically choose the correct backend
Date: Mon, 14 Jul 2008 17:43:53 +0200	[thread overview]
Message-ID: <487B7439.6060405@gmail.com> (raw)
In-Reply-To: <20080714145107.GC31522@suse.de>

Klaus Singvogel wrote:
> Till,
> 
> Till Kamppeter wrote:
> [...]
>> *cupsReplaceURI: "usb://HP/LaserJet(_|%20)42\d\d hp:/usb/HP_LaserJet_42\d\d"
>>
>> Here we do not use model info from the "lpinfo -l -v" output. The 
>> printer setup tool should match the first regexp against the user-chosen 
>> URI and the search the "lpinfo -v" output for an URI matching the second 
>> regexp.
> 
> This is not regex, it's perl extended regex you're using here. Maybe
> we run into trouble, if we extend CUPS tools by perl too.
> 
> We might want to use POSIX regex please, as defined in regex(7)?
>

Sorry for giving a bad example. All this was only a suggestion and not a 
spec. But I hope it shows the idea.

> I think, the rest of the discussion has to be answered by the author
> of "lpinfo" (= CUPS team). It's fine with me, if we extend CUPS in
> such a way.

They answered already in for them there should be only one backend per 
printer. They are working with HP now on making the "hp" backend 
unnecessary.

    Till


  reply	other threads:[~2008-07-14 15:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-19 21:52 [Printing-architecture] Printer setup tools: Automatically choose the correct backend Till Kamppeter
2008-06-20  5:59 ` Till Kamppeter
     [not found]   ` <4665C7B0F1146045A32E6AA72D0D62D741A40F26@G3W0634.americas.hpqcorp.net>
2008-06-23  6:47     ` Till Kamppeter
     [not found]       ` <200806231052.m5NAqQp7031706@dsl092-065-009.bos1.dsl.speakeasy.net>
2008-06-23 11:16         ` [Printing-architecture] [Gimp-print-devel] " Till Kamppeter
2008-07-14 14:45           ` Klaus Singvogel
     [not found]         ` <1214218973.4005.30.camel@cyberelk.elk>
     [not found]           ` <200806231111.m5NBB7eO031799@dsl092-065-009.bos1.dsl.speakeasy.net>
2008-06-23 11:23             ` Till Kamppeter
2008-07-14 14:39               ` Klaus Singvogel
     [not found]     ` <200806211529.m5LFTs8h007154@dsl092-065-009.bos1.dsl.speakeasy.net>
     [not found]       ` <c78a68b30806221102y1fd0d75m6424c2b55c573465@mail.gmail.com>
2008-06-23  7:02         ` Till Kamppeter
     [not found]           ` <200806231050.m5NAoRxO031694@dsl092-065-009.bos1.dsl.speakeasy.net>
2008-06-23 11:21             ` Till Kamppeter
     [not found]     ` <485EC26E.7090100@apple.com>
2008-06-23  9:19       ` Till Kamppeter
2008-07-14 14:51 ` [Printing-architecture] " Klaus Singvogel
2008-07-14 15:43   ` Till Kamppeter [this message]
2008-07-14 18:13     ` Klaus Singvogel

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=487B7439.6060405@gmail.com \
    --to=till.kamppeter@gmail.com \
    --cc=gimp-print-devel@lists.sourceforge.net \
    --cc=kssingvo@suse.de \
    --cc=printing-architecture@lists.linux-foundation.org \
    --cc=printing-foomatic@lists.linux-foundation.org \
    --cc=printing-japan@lists.linux-foundation.org \
    --cc=shiyun.yie@hp.com \
    --cc=suffield@hp.com \
    --cc=twaugh@redhat.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.