From: Solomon Peachy <pizza@shaftnet.org>
To: Zdenek Dohnal <zdohnal@redhat.com>
Cc: Open Printing <printing-architecture@lists.linux-foundation.org>,
Jai Luthra <luthrajaiji@gmail.com>,
Till Kamppeter <till.kamppeter@gmail.com>
Subject: Re: [Printing-architecture] Automatic printer setup with Printer Applications
Date: Thu, 25 Feb 2021 09:54:39 -0500 [thread overview]
Message-ID: <YDe6L+I0u65ncSXP@shaftnet.org> (raw)
In-Reply-To: <e9d76903-993c-7fd7-3a8d-809c176cc931@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1364 bytes --]
On Thu, Feb 25, 2021 at 09:28:47AM +0100, Zdenek Dohnal wrote:
> Solomon, I'm sorry if it is an obvious fact, but I don't know it - would
> you mind me asking why IEEE1284 IDs aren't used so much in drivers?
I can't comment on manufacturer-supplied/supported drivers, but speaking
of my own experience with Gutenprint we can't use what we don't know
about. The tooling that could take advantage of those IDs to
provide automagic printer setup didn't exist until relatively [1]
recently, and by then it was a bit too late..
And much like we've seen multiple distinct models with identical USB
VID/PIDs, I've also seen distinct models that share identical IEEE1284
IDs. [2] And then there's the iManufacturer/iModel/iSerial strings that
may or may not match what's in the 1284 data or what's silkscreened onto
the printer itself..
...Like everything else involving printing, it's a complete mess.
(Of the stuff in Gutenprint, about a quarter of the IEEE1284 IDs, and
all of the USB VID/PIDs, were added by myself.)
[1] ie about a decade ago.
[2] They are in the same family, but the PDL is barely incompatible..
- Solomon
--
Solomon Peachy pizza at shaftnet dot org (email&xmpp)
@pizza:shaftnet dot org (matrix)
High Springs, FL speachy (freenode)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-02-25 14:54 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 19:27 [Printing-architecture] Automatic printer setup with Printer Applications Till Kamppeter
2021-02-24 7:37 ` Johannes Meixner
2021-02-24 8:03 ` Zdenek Dohnal
2021-02-24 11:25 ` Till Kamppeter
2021-02-24 12:01 ` Johannes Meixner
2021-02-24 13:51 ` Till Kamppeter
2021-02-25 10:30 ` Johannes Meixner
2021-02-25 13:37 ` Till Kamppeter
2021-02-25 14:00 ` Johannes Meixner
2021-02-25 13:53 ` Michael Sweet
2021-02-24 12:48 ` Solomon Peachy
2021-02-24 14:01 ` Johannes Meixner
2021-02-24 17:23 ` Till Kamppeter
2021-02-26 9:17 ` Johannes Meixner
2021-02-24 14:17 ` Till Kamppeter
2021-02-25 15:28 ` Solomon Peachy
2021-02-25 22:54 ` Till Kamppeter
2021-02-26 14:59 ` Solomon Peachy
2021-02-25 8:28 ` Zdenek Dohnal
2021-02-25 14:54 ` Solomon Peachy [this message]
2021-02-26 10:03 ` Johannes Meixner
2021-02-26 12:28 ` Solomon Peachy
2021-02-27 21:07 ` Michael Sweet
2021-02-24 14:17 ` Michael Sweet
2021-02-24 14:46 ` Johannes Meixner
2021-02-24 18:47 ` Till Kamppeter
2021-02-24 17:40 ` Till Kamppeter
2021-02-24 17:48 ` Michael Sweet
2021-02-24 19:21 ` Till Kamppeter
2021-02-24 20:01 ` Michael Sweet
2021-02-24 20:15 ` Till Kamppeter
2021-02-25 8:52 ` Zdenek Dohnal
2021-02-25 9:24 ` Till Kamppeter
2021-02-25 9:54 ` Zdenek Dohnal
2021-02-25 13:43 ` Michael Sweet
2021-02-25 19:39 ` Till Kamppeter
2021-02-25 13:33 ` Michael Sweet
2021-02-25 15:24 ` Till Kamppeter
2021-02-25 15:30 ` Michael Sweet
2021-02-25 21:51 ` Till Kamppeter
2021-03-02 10:58 ` [Printing-architecture] Future of Printer Setup Tools Till Kamppeter
2021-03-02 12:04 ` Johannes Meixner
2021-03-02 22:52 ` Till Kamppeter
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=YDe6L+I0u65ncSXP@shaftnet.org \
--to=pizza@shaftnet.org \
--cc=luthrajaiji@gmail.com \
--cc=printing-architecture@lists.linux-foundation.org \
--cc=till.kamppeter@gmail.com \
--cc=zdohnal@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.