Linked by Thom Holwerda on Fri 16th Apr 2010 14:11 UTC
Google One of the major problems Google is facing with its Chrome OS is printer support. It was reported earlier that Google is working with manufacturers on making printers act similar to for instance digital cameras, so you won't need to fiddle with drivers any longer. It turns out Google has indeed been working on this, but I don't think the solution they unveiled today is what everyone had in mind - despite that, I'm seeing the value here.
Thread beginning with comment 419374
To read all comments associated with this story, please click here.
What you're looking for already exists...
by bhtooefr on Fri 16th Apr 2010 16:17 UTC
bhtooefr
Member since:
2009-02-19

It's called PCL5e and PCL5c.

Just avoid PCL6 "Enhanced" (another name for GDI - PCL6 Standard is just PCL5e and PCL5c renamed) printers, and just about anything from an Apple IIGS to a brand new machine with Windows 7 can print to a PCL printer.

Even quite a lot of HP inkjets use PCL5c.

Before anyone says PostScript... PCL is cheaper to implement, and can't do as much, but still just as standard.

Reply Score: 3

phoenix Member since:
2005-07-11

It's called PCL5e and PCL5c.


Yeah, wouldn't it be nice if companies would use the standards/protocols that are already out there, instead of developing their own, incompatible ones?

Do we really need PJL, HPIJS, HPIJL, SPLIX, etc?

Between PS, PCL, PPD, and IPP, we have the entire stack covered, with "drivers" being nothing more than simple text files. Just stick those into the device firmware, and have them "installed" as part of the USB device detection process, or as part of the "connecting to network device" process.

It's not rocket science. The tools are already there. All the building blocks are there.

And yet, none of the hardware manufacturers give a damn.

Reply Parent Score: 5

bhtooefr Member since:
2009-02-19

Well, PJL is part of the PCL spec - if not PCL1, then certainly by PCL2 or 3, IIRC.

Reply Parent Score: 1