From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: MIME-Version: 1.0 Date: Wed, 24 Feb 2021 15:01:56 +0100 From: Johannes Meixner In-Reply-To: References: <12af8541-3113-341d-6b7f-d7393203368f@gmail.com> <949aea1f-a0f0-df47-1538-d7782f5350ab@redhat.com> <66430674-dc47-4a81-406b-aedefc065a37@gmail.com> Message-ID: <9d87166cb02c637e30e7d165c8293275@suse.de> Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Printing-architecture] Automatic printer setup with Printer Applications List-Id: Printing architecture under linux List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: printing-architecture@lists.linux-foundation.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