Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!weretis.net!feeder4.news.weretis.net!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Unknown Newsgroups: comp.sys.raspberry-pi,comp.os.linux.misc,alt.os.linux.debian Subject: Re: HOW2 mobile, headless-rPi connect to LAN-printer? Date: Sat, 28 Mar 2015 09:21:30 +0000 (UTC) Organization: A noiseless patient Spider Lines: 56 Message-ID: References: <20150325180540.5fe7b534@jresid.jretrading.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Sat, 28 Mar 2015 09:21:30 +0000 (UTC) Injection-Info: mx02.eternal-september.org; posting-host="b9559e00794aaa08ec1758553325b866"; logging-data="17270"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+3iFOoBwJOQtTF9Aemffhtyj1MFfvz5ag=" User-Agent: Pan/0.133 (House of Butterflies) Cancel-Lock: sha1:I7dp80qPPvsPDUOwoBkZE9DfvbI= Xref: csiph.com comp.os.linux.misc:14264 On Thu, 26 Mar 2015 14:03:37 +0000, The Natural Philosopher wrote: > On 26/03/15 13:30, Dan Purgert wrote: >> what TCP9100 was used for back then > > Basically its about as high level as a parallel serial or USB port. 9100 > was a RAW protocol. > > How to get bytes from computer to printer. They still need to be the > RIGHT bytes. > > > MOST printers today are postcript capable and that means CUPS =- which > is very very postcript oriented - will be able to make a stab at > supporting them. > > Problems occur with winprinters that accept some weird PCL language that > need a special rasterisation setup to accept a full image or > postscript-in-a-weird-font type stuff, or need special commands to > select specail features like duplex printing. > > The latter can be handled by writing a PPD file. I've actually dome that > for a printer that wasn't fully supported. > > > But rasterisation may be more difficult. I am not sure how cups handles > that. > > It seems on research there are a bundle of image and postcript to raster > programs that cups uses - these should be totally portable to any > architecture, and therefore part of any full CUPS and Ghostscript port. > > And PPDs are just text files. > > So I would say there is no part of CUPS that requires an architecture > specific device driver beyond USB, serial, parallel or tcp socket level. > > So cups on a Pi should 'just work' *once set up*. As well as it does on > *86. > > Now of the 'printer discovery tools' that allow automagic detection and > installation of network printers, that is another matter. > > Id google bonjour, as that seems to be the latest wheeze. -- Obviously, many writers here are 'in the industry'. So for them: the more complex the better. But how/why do you USERS tolerate the absurdity: compared to printing a page of plain text 40 years ago?! If you examine a typical http of a big organisation, via lynx today, each "page" is 95% redundant/repeated garbage; for 5% new info. The kiddies cheer-on-with-delight each new layer of complexity. It's like the lawers: "why use 10 words, when 10'000 will do?"