From: Johannes Meixner <jsmeix@suse.de>
To: printing-architecture@lists.linux-foundation.org
Subject: Re: [Printing-architecture] Automatic printer setup with Printer Applications
Date: Wed, 24 Feb 2021 15:01:56 +0100 [thread overview]
Message-ID: <9d87166cb02c637e30e7d165c8293275@suse.de> (raw)
In-Reply-To: <YDZLEKxaIVrpLm4E@shaftnet.org>
Hello,
On 2021-02-24 13:48, Solomon Peachy wrote (excerpt):
> And as a depressing data point, Gutenprint only has
> IEEE1284 IDs for about 15% of its supported models, and
> USB VID/PIDs for about 3%. So a mechanism to auto-match
> based on the Manufacturer & Model strings out of the USB
> or IEEE1284 descriptors would still be a good idea..
I had experienced in the past some overenthusiastic
"let's simply just collect printer IEEE1284 IDs" or
"let's simply just collect printer USB VID/PIDs"
attempts by overenthusiastic wishful-thinkers
that appeared every now and then but never ever it
resulted really useful data - only duplicates for
well know printer devices like some HP LaserJets
but basically nothing for all those zillions of
printer devices that manufacturers continuously spill out
and unexperienced end-users "just buy" in the next shop.
I took me some longer time of experience what works
reasonably well in practice out there in real world
how to auto-match based on the manufacturer & model
strings which is the only data that is always there.
So a 90% working auto-match based on the manufacturer & model
works in 90% of the cases in practice out there in real world
while a 100% working auto-match based on IEEE1284 IDs or
USB VID/PIDs works only in less than about 20% of the
cases in practice out there in real world.
My auto-match based on the manufacturer & model strings
is in SUSE's YaST2 printer module in somewhat human readable
form only in my old YCP code (the new autogenerated Ruby code
is no longer actually human readable - at least not for me).
I could try to dig that out but I fear what comes out is a pile
of hacks that I just somehow put together to make that stuff
work reasonably well in practice out there in real world.
Kind Regards
Johannes Meixner
--
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5 - 90409 Nuernberg - Germany
(HRB 36809, AG Nuernberg) GF: Felix Imendoerffer
next prev parent reply other threads:[~2021-02-24 14:01 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 [this message]
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
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=9d87166cb02c637e30e7d165c8293275@suse.de \
--to=jsmeix@suse.de \
--cc=printing-architecture@lists.linux-foundation.org \
/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.