Patent Applications Hint Apple Wants To Eliminate Printer Drivers 323
An anonymous reader writes "Apple has filed two patent applications that describe an approach as well as file formats and APIs to eliminate the printer driver as a requirement for users to access a printer and print documents. If the company has its way, there will be three ways to access a printer in the future: The first will be via a conventional software driver. The second will be via a cloud service and the third will be via a driverless access method that supports 'universal' printing from any type device."
postscript (Score:5, Insightful)
Wasn't postscript supposed to solve these problems 20 years ago?
Re:postscript (Score:5, Interesting)
And it did a great job. Aren't the patents on PostScript expired by now? And the microprocessor and memory needed to run it is now dirt cheap.
Years ago getting printers to work on Linux was a major pain, and often the output didn't look that great. But if you had a postscript printer, it was a 3 second setup. Quite a bit like configuring a real SoundBlaster for Linux compared to some no-name 3rd party piece of junk.
Re:postscript (Score:5, Informative)
Well patents expiring helped a lot.
But in reality, virtually every postscript printer came with a PPD, and that PPD was all you ever needed to get a postscript printer running on linux. A PPD file is non OS specific.
But given Apple's overly litigagatory stance on any thing they (claim to) develop, I just don't see any of their suggestions getting accepted.
I can't see anyone opening themselves up for that kind of lawsuit until or unless Apple puts it all under the GPL or some other free license.
Postscript is free and everybody uses it. It pretty much renders page preparation a non issue, because virtually all postscript printers will use the default PPD in a pinch, albeit with somewhat more limited capabilities. Printers do have different capabilities and you must make allowance for that, but postscript handled that very nicely.
Re: (Score:2)
Given that they already open sourced CUPS, and don't have any profit in printers, it's more likely than not they would simply open source it like OpenCL, CUPS, Webkit, etc.
Re: (Score:3)
Given that they already open sourced CUPS, and don't have any profit in printers, it's more likely than not they would simply open source it like OpenCL, CUPS, Webkit, etc.
This is Slashdot - if it's not released under the GPL, it doesn't count as open source and should be ridiculed.
Re: (Score:2)
Cups was already opensource when they bought it. The didn't have much choice. Webkit same deal. It was GPL when they grabbed it, and after a fairly long fight they decided to give their changes back to the KDE community from which it sprang.
Re: (Score:2)
The rest of your post was so thoughtfully composed, I felt like you might want to know that it's just 'adhere'.
http://www.merriam-webster.com/dictionary/adhere [merriam-webster.com]
Re: (Score:2)
Good catch. I tend to save my best spelling for those that pay me. ;-)
Re: (Score:2)
Apple stone walled KDE for a couple years until their own lawyers pointed out to them that they had to ad-hear to the GPL.
No. Safari (and what was to become Webkit) was announced at Job's 2003 Macworld keynote. The code was released the same day. [kde.org]
You are correct that the form of the changes was unusable according to KDE developers (which was soon rectified) but Apple contributed code from day 1 (actually, before day 1 [archive.org] in the case of JavaScriptCore.)
Re: (Score:3)
Given that they already open sourced CUPS,
Actually, CUPS was developed before, and was open source before, Apple hired its creator (who is, BTW, the first inventor in the list in the patent application).
Partial reality distortion? (Score:3)
Given that they already open sourced CUPS, and don't have any profit in printers, it's more likely than not they would simply open source it like OpenCL, CUPS, Webkit, etc.
Apple developed OpenCL [wikipedia.org] and open-sourced it under the permissive GPL. Kudos for that.
However, CUPS [wikipedia.org] existed and was open-source for years before Apple adopted it in 2002 (they did not create it).
Webkit is a fork of the KHTML [wikipedia.org] library which is and was under the LGPL, and thus Apple had no choice over open-sourcing it and releasing it under a permissive license.
Re: (Score:2)
Given that they already open sourced CUPS, and don't have any profit in printers, it's more likely than not they would simply open source it like OpenCL, CUPS, Webkit, etc.
Apple developed OpenCL [wikipedia.org] and open-sourced it under the permissive GPL. Kudos for that.
However, CUPS [wikipedia.org] existed and was open-source for years before Apple adopted it in 2002 (they did not create it).
Webkit is a fork of the KHTML [wikipedia.org] library which is and was under the LGPL, and thus Apple had no choice over open-sourcing it and releasing it under a permissive license.
WebKit started as a fork and was completely rewritten. Nothing of KHTML/KJS is in WebKit. Apple took over sponsorship of CUPS and it's creator works for Apple. All but the interfaces within OS X have been released to the public.
Re: (Score:3)
I somehow doubt that, not least because totally rewriting Webkit would require breaking a lot of stuff for no good reason. (Also, Webkit and KHTML often have the exact same bugs...)
Re: (Score:3)
Chris Lattner started LLVM while in university, at least 5 yrs before Apple hired him. I gave Redhat top marks for a company contributing to open source and they seem to be the only ones who have yet to descend into assholery.
Re:postscript (Score:5, Informative)
Wrong. Apple did no such thing. CUPS has been around as open source since 1997 - the GPL, to be precise:
Michael Sweet, who owns Easy Software Products, started developing CUPS in 1997. The first public betas appeared in 1999.[3] The original design of CUPS used the LPD protocol, but due to limitations in LPD and vendor incompatibilities, the Internet Printing Protocol (IPP) was chosen instead. CUPS was quickly adopted as the default printing system for several Linux distributions, including Red Hat Linux.[citation needed] In March 2002, Apple Inc. adopted CUPS as the printing system for Mac OS X 10.2.[4] In February 2007, Apple Inc. hired chief developer Michael Sweet and purchased the CUPS source code.[5]
And you seem to be implying that Apple open sourced Webkit, etc. (BSD? anything else you'd like to make wild claims about?) as well? Bull fucking shit. Webkit originated in KDE (more or less, it may have heritage beyond that). OpenCL is indeed Apple, but it's not open source, either.
Did Apple make Samba, Apache, and Postscript, too? (The answer is no.) Apple is no "proponent" of "open source"; they're a proponent of free software. There is a huge, huge difference, particularly when they are the sole financial benefactor involved.
I'm so sick and tired of Apple fanboys saying "it was done on the mac, first!" when the reality is often quite different. Apple gets credit for improving upon CUPS, sure. But not much beyond that (and even that is tenuous to argue).
Re: (Score:2)
Printers do have different capabilities and you must make allowance for that, but postscript handled that very nicely.
How does it handle "the ability to interpret PostScript is not one of this printer's capabilities"? :-)
Re: (Score:2)
Re: (Score:2)
I don't know offhand - go on back to 1995 and ask someone? ;-)
Why not ask them now? There were non-PostScript printers then, and there are non-PostScript printers now (i.e., "everybody uses it", where "everybody" includes "printer vendors", is a false statement).
Re: (Score:2)
Re: (Score:3)
You use middleware in between the printer and the end user tools.
This was being done by Linux in the 90s and SunOS in the 80s.
Re: (Score:2)
tl;dr
Postscript rules. Apple drools.
Re: (Score:2, Informative)
Litigagatory?
Ouch! Looks like the famous *gatory factory is working at full speed.
In English there already exists a word for persons inclined towards litigation. It's litigious.
Re: (Score:2)
The beauty of english is the ability to create alternative forms, all of which are equally valid. In this case the gatory factory has been hard at work since 1860, even if it is a surprise to you.
Litigatory actually predates litigious [google.com] by well over a hundred years.
Re: (Score:3)
But in reality, virtually every postscript printer came with a PPD, and that PPD was all you ever needed to get a postscript printer running on linux. A PPD file is non OS specific.
And these days ... surely there's a standard available to get the PPD from the printer by now?
GET /ipp/ps/ppd HTTP/1.0
or something? Find the printer via multicast-DNS and go on with your day?
Re: (Score:3)
Well then I'm guessing 10 years ago was probably the last time you bought a printer then.
You are hard pressed to find any modern printer that DOESN'T support postscript.
Check the specs on what you have nearby. You' will probably be surprised.
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
Re: (Score:3)
Not worth it.
As an add on it isn't that bad, but if you require drivers to print then it's a huge step backwards. One of the reasons I went for the Mac version of my Laserjet was because FreeBSD was a lot easier to set up with a postscript printer. Printer companies don't typically release drivers for all possible platforms and Postscript was a god send for those not using a supported OS.
Sure it's nice to be able to check levels and all that, but it's hardly essential, and not worth giving up the ability to
Re: (Score:3)
Printer drivers are necessary in many cases because non-Apple printer vendors support a very wide and differing feature set.
You are aware that the sets "non-Apple printer vendors", at least in the sense of "printer vendors other than Apple", and "printer vendors" are the same? I.e., there are no Apple printers.
Re: (Score:2)
there are no Apple printers.
Tomorrow when I get home, please remind me to check whether my ImageWriter II (impact printer used with my Apple IIGS) and my Color StyleWriter 2500 (a rebadged Canon BubbleJet) are still in my basement, or whether they've evaporated. (References here [wikipedia.org])
Serious mode: Apple printers still exist; they're just discontinued.
Re: (Score:2)
Serious mode: Apple printers still exist; they're just discontinued.
Yes, I know about the LaserWriter, etc., so "there are no Apple printers any more", then. The point is that you can't rationally argue that Apple can solve this problem because the printers they design have limited capabilities, and thus need no drivers, as they haven't designed printers in ages (and the first one they designed was a PostScript printer, so you could send it arbitrary programs - hardly "very locked-down and limited to a small set of functionality".
Sincerely, Frustrated Moderator (Score:2)
I have mod points, but I won't spend them, because I can't mod you both +1 insightful and -1 flamebait.
And if I could do so, the net mod would be +0:Ambivalent.
You have some great points, truly, but it's completely neutered by the Apple hater verbiage at the end. Leave the "social rejects" out of it, and it's a cogent and insightful post.
Re: (Score:2)
Apple also sells a lot of stuff to pensioners (or "seniors" as I supposed they're referred to in America).
My dad's laptop recently died and I ended up convincing him to get an iPad, which he loves. All he wants is web, email, maps, BBC iPlayer and the odd film. He hated it when his laptop was slow or had any sort of technical issue and never installed any applications on it, so the iPad is a perfect replacement.
Apparently you can also buy blood pressure monitoring peripheral for it, which made my mum giggle
Re: (Score:2)
Cool, so it's totally ok to refer to all Linux users as parental-basement dwelling neckbeards with hygiene and attitude problems.
Just checking, since it's ok to "accurately describe" Apple users as "trust fund babies and social rejects".
Re: (Score:2)
1.Embrace
2.Extend
3.Extinguish
Re: (Score:2)
It was indeed the first commercially available printer to implement PostScript, and hit the market in 1985.
Adobe began working on PS itself in 1982, and released it to market in late 1984, so if there was a patent on it, it's expired by now. Ahh, but Apple is talking about doing it bidirectionally over USB, so clearly it's a new technology.... we have stumbled on the reason they got rid of legacy ports!
Re: (Score:3)
How many printers have access to the 'net? And if the printer is attached via USB to your home computer, isn't that kind of insecure to have a "cloud" service that can reach your home printer by going through your home computer? I suppose that if I have an Airport Extreme with a USB printer attached or a Wi-Fi printer... And who prints any more anyway? I ran out of ink about
Re: (Score:3)
How many printers have access to the 'net?
More and more of them these days - wireless networking is rapidly becoming the norm in even cheapie consumer inkjets. Apple aren't thinking about the printer you buy today, they're thinking about the printer you might buy in 2-3 years time.
Re: (Score:3, Interesting)
> my phone can see the printer via wifi and it detects make/model and sends a request to the internet,
> where my print job is magically turned into something recognized by the printer.
Someday.... Meanwhile today a Linux or Mac with CUPS works. Some printers even support it native. Imagine today you wander into a WiFi net with a CUPS server and you just see printers magically appear in your list. You get a PPD delivered automagically so you see all of its features, color, duplex, paper trays and fin
Re: (Score:3)
mmmm (Score:2)
Re: (Score:2)
what i never understood was why was there never wide spread support for the USB printer class. I mean, HID did wonders for joypads and all sorts of other input devices. Why did printer vendors fore go sanity with their software support?
Re: (Score:3)
USB printer class doesn't describe the language that the printer uses, only the way that print data is transported between the host and printer. It's designed to encapsulate any form of print data, be it PostScript, PCL, or something proprietary.
Re: (Score:2)
Re:mmmm (Score:5, Informative)
This might be one of those patents that a company like Apple files for defense purposes especially with their CUPS and Bonjour work
THEIR CUPS?
Michael Sweet, who owns Easy Software Products, started developing CUPS in 1997. The first public betas appeared in 1999. The original design of CUPS used the LPD protocol, but due to limitations in LPD and vendor incompatibilities, the Internet Printing Protocol (IPP) was chosen instead. CUPS was quickly adopted as the default printing system for several Linux distributions, including Red Hat Linux.[citation needed] In March 2002, Apple Inc. adopted CUPS as the printing system for Mac OS X 10.2. In February 2007, Apple Inc. hired chief developer Michael Sweet and purchased the CUPS source code.
Cups was Open Source for 6 years [wikipedia.org] before Apple supposedly bought it.
Re: (Score:3)
Re: (Score:2)
Apple didn't buy the Cups source code [...] Apple bought the copyright to the Cups source code
"Purchased a work of authorship" can mean one of two things: buying a copy or buying an assignment of the copyright. In context, the latter interpretation appeared obvious to me, especially right after "hired chief developer".
Re: (Score:3)
Like I say, it was open source GPL in many different Linux distros for years before Apple got involved.
Since it was GPL, just what did Apple buy? Oh, they bought the developer. Figuratively and Literally,
and pretty much induced him to walk away from his own GPL declaration "Just for them"..
Copyright 1997-2006 by Easy Software Products
Re:mmmm (Score:5, Informative)
If you buy the copyright to a GPL'd work, it is yours. You can change the license to anything you want. You can't change the already released versions, of course, but anything from that point onwards is entirely up to you.
Re: (Score:2)
Michael Sweet, who owns Easy Software Products,
...and works for Apple Inc. on printing and has his name as the first inventor on the patent in question.
Re: (Score:2)
"supposedly"
What, is it not ok for the original owner of the code to sell it? I thought that was ok in the open source world, or is making money verboten?
Apple sunk money and time into it because they appreciated its value, and the value of the guy who started it in the first place, in much the same way as they did with KHTML.
Since they *did* buy the rights to the code, it is accurate to describe it as "theirs", although that doesn't mean "they did all the work".
Re: (Score:2)
How else are they going to cram 600MB of shovelware down your throat?
Of course, this isn't really driverless printing, it's just a matter of where the driver lives. Eventually, either the printer has a driver built in or the computer that talks to it does (or both).
This will likely end up being yet another one true universal data format that will be demanded by a minority of software. As long as a patent hangs over it, it will not reach 100%.
Patent != Product (Score:3)
As we're all aware, one of the problems with the patent system is that patents don't always equal products. How many times has an Apple patent made the news with no product to show for it? How many people missed the iPhone because they weren't paying attention to the right patents?
That being said, this is WAY more plausible given Apple's work with CUPS and AirPrint.
Re: (Score:2)
Patents shouldn't always equal products sometimes a valid patent requires technology that nobody can get to work at the present. However, there should be a requirement that you're using it or are in the process of bringing a product to market. Just filing for a patent does benefit the public as it's then available for use when the patent expires.
The main problem is folks that file papers with no intention of turning it into a real product and who sue without even attempting to produce anything.
So what? (Score:2)
Option 2: Send it to the cloud, which just basically uses someone else's driver.
Option 3: Standardize all printers to communicate in exactly the same way, making a "one-size-fits-all" driver.
I don't really see the "elimination" part here. Maybe a "simplification" at best.
Re: (Score:2)
PDF? Isn't that the general idea behind the "portable document format"? Send a PDF to the printer, call it a day. If they can print jpegs directly off memory cards that would seem like a relatively easy approach to a driverless system.
Re: (Score:2)
If they can print jpegs directly off memory cards
That involves resizing the picture to fit the paper, something that end users find acceptable for photographs, not so much for text.
Re: (Score:3)
Monochrome is pretty easy to do with PDF. Duplex might be a bit trickier.
Re: (Score:2)
Option 4: let printers say what formats they accept (PostScript, PDF, JPEG, rasters, etc.) and send them the most appropriate format for the particular print job. Read The Fine Patent Application (for which I'll post a link in a comment).
No matter what it won't get rid of it (Score:3)
While a standardization of features could make ti so you don't need a 3rd part driver for simple things, you still need a driver and you need a more complex one for full support.
If you want to see an area where this has happened, look at audio on Windows. Microsoft laid out the specs for the Universal Audio Architecture. As the name implies, it is a set of audio standards. For Vista and later, to get the logo you need to have a sound card that complies with it to the extent that it can function with no driv
Comment removed (Score:3)
Re: (Score:2)
Paper is not one-product away from majorly dropping in popularity. It'll be around when we're buzzing planets in our flying saucers.
Re: (Score:2)
right when they're making tablets so popular that we don't need hard copy anymore.
Surely you jest. Even if tablets become absolutely, positively dirt cheap, they still won't be a proper replacement for paper documents.
Smartphone (Score:2)
There's no way I can ever conceive of lugging a tablet around with me just going about everyday tasks
Let me guess: man who wouldn't be caught dead with "a purse". I have a bag for my netbook.
for really important documents I want a paper backup that I can still access in case of a power outage.
How long do you expect such outages to last?
With an electronic copy, we need some kind of digital device to accommodate the transfer
Such device could be a mobile phone. I'm under the impression that it has become customary to carry a mobile phone in case of needing to make an urgent call, such as car/bike trouble or notifying someone of one's impending arrival at the locked front door of a multiple-story apartment. The one wrinkle could be that o
Re: (Score:2)
I live in the second largest city in Australia. I work in a building which houses several engineering firms and the state police. Tablets are everywhere. Go out for coffee and there will be a tablet on every fourth table or so. Though I think it is a bit of a fad. I think tablets will take a stable chunk of the light laptop use case in the long term.
xkcd is their inspiration (Score:2, Funny)
http://xkcd.com/927/ [xkcd.com]
I was thinking College Humor (Score:2)
This is what I thought of when I read the summary: http://www.collegehumor.com/video/3915385/your-printer-is-a-brat [collegehumor.com]
never gonna happen (Score:5, Informative)
Nearly all consumers want CHEAP printers. That means that the translation from text/image to printer imaging codes is done in the computer, not the printer, which saves CPU power and memory in the printer. Look at the difference in price between the typical Windows printer and the Postscript ('specially color) printers. A Windows printer only has to buffer a few raster lines, using the processing power and memory of the host computer, while the Postscript printer has to buffer the entire page, since there could be a command at the end of the page that places something at the top.
Add to this the insanity of any/all software and process patents and it is absolutely in the printer manufacturers' interest to tie the raster-defining codes into obscure and NDA-protected proprietary drivers to avoid tripping over some patent that says " a one bit in this field says put a green dot next on the page".
Re:never gonna happen (Score:5, Insightful)
Nearly all consumers want CHEAP printers. That means that the translation from text/image to printer imaging codes is done in the computer, not the printer, which saves CPU power and memory in the printer. Look at the difference in price between the typical Windows printer and the Postscript ('specially color) printers. A Windows printer only has to buffer a few raster lines, using the processing power and memory of the host computer, while the Postscript printer has to buffer the entire page, since there could be a command at the end of the page that places something at the top.
Add to this the insanity of any/all software and process patents and it is absolutely in the printer manufacturers' interest to tie the raster-defining codes into obscure and NDA-protected proprietary drivers to avoid tripping over some patent that says " a one bit in this field says put a green dot next on the page".
You have a good point 10 years ago. Today, processors and memory are so cheap that you could build an entire computer into a printer and still sell it for $150. See also: netbooks, handheld gaming devices, mobile phones.
Re: (Score:3)
you could build an entire computer into a printer and still sell it for $150
You missed the part where he said "CHEAP", right? $50 or less.
Re: (Score:2)
I would consider the HP Color Laserjet 2025dn to be a cheap (for a duplex color laserjet) printer which supports HP's postscript 3 emulation.
Re: (Score:2)
Nearly all consumers want CHEAP printers. That means that the translation from text/image to printer imaging codes is done in the computer, not the printer, which saves CPU power and memory in the printer.
Which means that, to quote the patent, "the information indicates the printer can only support RF", where "RF" means "Raster Format", and therefore that "the system uses RF to send data to the printer".
Re: (Score:2)
Just about all Consumer Printers now support PictBridge, which is practically a Driverless Printing Protocol (or a common-driver Printing Protocol).
HP's ePrint Printers already Behave similar to this, and most of HP's non-ePrint Printers support PCL3 too.
The main reason Drivers are required for printers currently is to gain mindshare on users computer. Snow Leopard's excellent native Driver Support and Windows 7's Device Stage reduce the annoying Product Ads the User is exposed to. Nowadays, the only reason
Re: (Score:2)
Apple's printer support is pathetic.
A printer (Xerox Phaser 6100) which had a Tiger driver, and is still supported quite nicely in CUPS elsewhere is NOT supported in Snow Leopard or Lion. Her MacBook is the last Apple my wife gets to use, since she relies on me for support, and I'll never do another for her.
Re:Cheap (Score:2)
I don't want a cheap printer, I want a printer that is cheap to operate. The cheaper the printer, the more the ink cartridges (or whatever) will cost you, the sooner it will break or be abandoned etc. I bought an Laserprinter years ago that would print something like 6000 pgs per laser cartridge. The carts cost $120 or so and the printer cost me $300 plus, but it was far cheaper than replacing the ink carts in a cheap printer continuously at $45-75 each (as with the current printer we have). The only reason
Re: (Score:2, Informative)
Which would be important if:
A) PS memory/processing requirements were large by modern standards. They aren't. In 1987 you needed server-class CPU and memory to render PostScript. Today you need a 1987 server-class CPU and memory to render PostScript -- i.e. a 10 MHz processor and 8 MB of RAM. Neither of which has any significant cost even when you're talking about sub-$100 consumer equipment.
B) If writing and maintaining driver software was free. It's not. If you sold PS-capable printers you could write *no
Re: (Score:2)
Airprint (Score:3)
* With iOS
Re: (Score:3)
PictBridge eliminated Drivers years ago. If it hadn't Camera Firmware would have been bloated and would have needed updating constantly as new Printers came available.
HP ePrint (which AirPrint uses) is based on PCL5 which is Page Description Language like PostScript and PDF.
Rendering a Word or Pages document to a ePrint Printer still requires a driver to convert the RAW GDI of Windows, the PDF of Mac OS X or the PS of Linux to PCL5.
I may be corrected, but either all ePrint-compatible devices (iOS, WebOS) ha
Re: (Score:2)
Printer Object (Score:2)
I don't know why the OS can't have a Printer superclass that apps all call with a single unified print API, but that the specific instance of attached printer overrides with a subclass implementing the same interface but in that printer's own ways. Printers are all USB, and can install their subclass when plugging in.
Sure, that's a lot like a driver, but the users and programmers never notice anything but calling members of the Printer object. So the reasons for eliminating "drivers" are satisfied by doing
Re: (Score:2)
Printers are all USB
No, they're not. They might be networked printers; the patent makes references to IPP.
So the reasons for eliminating "drivers" are satisfied by doing it this way.
The reasons for eliminating drivers as listed in the patent are
Re: (Score:2)
TCP/IP printers should do the same thing, when the printing host connects to it the first time - respond with its ThisPrinter subclass.
The Printer superclass in the printing host's OS would have the basic printing API implemented as clients to the remote printer's server, where the rest of the code is stored.
Re: (Score:2)
The device doesn't need to find a printer driver. When it is first connected to the printer, the printer hands its driver over the connection to the device.
Re: (Score:2)
The device doesn't need to find a printer driver. When it is first connected to the printer, the printer hands its driver over the connection to the device.
Yeah, lets run random code downloaded from a random device when we connect to it. That sounds like a great plan.
Even assuming that the printer includes a driver that the device can run.
Re: (Score:2)
The difference is that what I described gives the device the connected printer's driver object when the device first connects to the printer. I described it in OOP terms because that's the best way to describe these things generically, in terms of the things and their interfaces. And because OSes are written in OOP - for that very reason.
dont know whether to laugh or cry (Score:3)
To Read The Fine Patent Application... (Score:5, Informative)
It's Patent Application 20110194140 ; here's the application [uspto.gov].
And, yes, that's Michael "Mr. CUPS" Sweet in the Inventors list.
Re: (Score:3)
It's Patent Application 20110194140 ; here's the application [uspto.gov].
And the other one is Patent Application 20110194124 [uspto.gov].
Not quite accurate (Score:2)
Screw the cloud (Score:2)
I say eff the cloud and everything about it. To me, it represents nothing more than a way to extract fees from you every month.
The first would be via software driver (Score:2)
Pointless (Score:2)
Re: (Score:2)
Then why do Macs work that way, too? They're not Windows, and they weren't Intel until recently - and didn't have to do Intel the way MS does.
Re: (Score:3)
so like a standard Printer Control Language or maybe some sort of Script for Posting thins to a printer... I wish someone would have thought of that sooner.
No, nothing like that. As noted in this comment [slashdot.org], there are a lot of cheap non-PostScript printers out there; in the scheme described in the patent, a printer could say "hey, I do PostScript" and the print system could send PostScript to the printer, just as it could say "hey, I do JPEG" and, if what's being printed is a JPEG image, the print system could send the JPEG to the printer, or it could say "hey, I do PDF" and the print system could send a PDF to the printer, or it could say "hey, I only do raster
Re: (Score:2)
Re: (Score:2)
there are a lot of cheap non-PostScript printers out there
So, the printer manufacturer's choice is:
1. License PostScript from Adobe.
2. License this new protocol from Apple.
Either way, the result won't be 'cheap' anymore.
and ink at 50%-200%+ mark up (Score:2)
and ink at 50%-200%+ mark up
Re: (Score:2)
In fact, wasn't it Apple that pioneered the adoption of PostScript? For both printing and screen rendering, IIRC.
Perhaps they just forgot to patent it back then. Someone moved a filing cabinet and found the original application that had fallen behind it.