This is a multipart MIME message. --==_Exmh_-19284503880 Content-Type: text/plain; charset=us-ascii
Hi, I recently added a new "hpoj" SANE backend to the CVS repository of the HP OfficeJet Linux driver project (http://hpoj.sourceforge.net), with support for SANE-based scanning on almost all HP OfficeJet, LaserJet, and PSC (Printer/Scanner/Copier) multi-function peripherals. My intention is to distribute it as part of the hpoj software rather than with SANE, due to the dependency problems and usability issues associated with having to specially compile SANE with the needed hpoj libraries (libptal and libhpojip), as is the case today with activating the OfficeJet support in the hp backend. Would somebody please check into SANE CVS the attached hpoj.desc file, which has linkages to my project page? I ran it through the sane-desc.el converter to make sure it looks OK in HTML format. Also, the link to the hpoj project on the SANE "Related Projects" page can now be moved to a different category from "not SANE compliant". :-) Once I make a new stable release of the hpoj software (with the hpoj backend) several months from now, I will submit a patch to remove the OfficeJet support from the hp backend and documentation, because the new hpoj backend is a replacement that supports more models and better handles the various OfficeJet-specific peculiarities such as ADF control and JPEG decompression and is much easier for me to maintain as an integrated package (just like the devices it supports:-). On a related topic as a follow-up to the recent discussion on adding new device types to the SANE standard, the hpoj backend supports a wide variety of devices with different ADF/flatbed capabilities: flatbed_only, scrollfed_only, flatbed+ADF, and flatbed+scrollfed_ADF. Currently the SANE standard specifies "flatbed scanner" and "sheetfed scanner" (among others). Would it be acceptable for me to use a more generic string such as "multi-function peripheral" or "all-in-one" so I don't have to return a different string based on the device's ADF/flatbed capabilities? That would also make sense because I will likely add fax-receive support to a future version of the hpoj backend. (I apologize for not bringing this up earlier when Henning was soliciting input on this matter.) David --==_Exmh_-19284503880 Content-Type: text/plain ; name="hpoj.desc"; charset=us-ascii Content-Description: hpoj.desc Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="hpoj.desc" Owo7IFNBTkUgQmFja2VuZCBzcGVjaWZpY2F0aW9uIGZpbGUKOwo7IEl0J3MgYmFzaWNhbGx5 IGVtYWNzLWxpc3AgLS0tIHNvICI7IiBpbmRpY2F0ZXMgY29tbWVudCB0byBlbmQgb2YgbGlu ZS4KOyBBbGwgc3ludGFjdGljIGVsZW1lbnRzIGFyZSBrZXl3b3JkIHRva2VucywgZm9sbG93 ZWQgYnkgYSBzdHJpbmcgb3IKOyAga2V5d29yZCBhcmd1bWVudCwgYXMgc3BlY2lmaWVkLgo7 CjsgIjpiYWNrZW5kIiAqbXVzdCogYmUgc3BlY2lmaWVkLgo7IEFsbCBvdGhlciBpbmZvcm1h dGlvbiBpcyBvcHRpb25hbCAoYnV0IHdoYXQgZ29vZCBpcyB0aGUgZmlsZSB3aXRob3V0IGl0 PykuCjsKCjpiYWNrZW5kICJocG9qIiAgICAgICAgICAgICAgICAgICA7IG5hbWUgb2YgYmFj a2VuZAo6c3RhdHVzIDpiZXRhICAgICAgICAgICAgICAgICAgICAgOyA6YWxwaGEsIDpiZXRh LCA6c3RhYmxlLCA6bmV3Cjp1cmwgImh0dHA6Ly9ocG9qLnNvdXJjZWZvcmdlLm5ldC8iIDsg YmFja2VuZCdzIHdlYiBwYWdlCgo6ZGV2aWNldHlwZSA6c2Nhbm5lciAgICAgICAgICAgICAg OyBzdGFydCBvZiBhIGxpc3Qgb2YgZGV2aWNlcy4uLi4KICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgIDsgb3RoZXIgdHlwZXM6ICA6c3RpbGxjYW0sIDp2aWRjYW0sCiAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICA7ICAgICAgICAgICAgICAgOm1ldGEsIDph cGkKCjptZmcgIkhQIiAgICAgICAgICAgICAgICAgICAgICAgICA7IG5hbWUgYSBtYW51ZmFj dHVyZXIKOnVybCAiaHR0cDovL3d3dy5ocC5jb20vZ28vYWxsLWluLW9uZSIKCjsgbmFtZSBt b2RlbHMgZm9yIGFib3ZlLXNwZWNpZmllZCBtZmcuCjptb2RlbCAiTW9zdCBIUCBtdWx0aS1m dW5jdGlvbiBwZXJpcGhlcmFscyIKOnVybCAiaHR0cDovL2hwb2ouc291cmNlZm9yZ2UubmV0 L3N1cGxpc3Quc2h0bWwiCjppbnRlcmZhY2UgIlBhcnBvcnQoRUNQKSBVU0IgSmV0RGlyZWN0 Igo6Y29tbWVudCAiRGlzdHJpYnV0ZWQgd2l0aCB0aGUgSFAgT2ZmaWNlSmV0IExpbnV4IGRy aXZlciAoaHBvaikiCgo7IDpjb21tZW50IGFuZCA6dXJsIHNwZWNpZmllcnMgYXJlIG9wdGlv bmFsIGFmdGVyIDptZmcsIDptb2RlbCwgOmRlc2MsCjsgIGFuZCBhdCB0aGUgdG9wLWxldmVs Lgo= --==_Exmh_-19284503880--