4 ms·
To be fair, printing in 1995-6 was a huge can of worms and hell on earth.
by bombcar 2y ago
To be fair, printing in 1995-6 was a huge can of worms and hell on earth.
- KerrAvon 2y agoISTR those of us using HP or Apple printers were generally in pretty good shape at the time. Can’t vouch for other brands.
- p_l 2y agoApple didn't support anything other than PostScript natively at the time, so their printers came with postscript support. HP made special models for use with Macs that shipped with PostScript included.
- tonyedgecombe 2y agoApple sold a ton of printers without PostScript: https://en.wikipedia.org/wiki/List_of_Apple_printers https://en.wikipedia.org/wiki/List_of_Apple_printers The earliest ones pre-dated PostScript by years.
- wbl 2y agoSend PostScript, done. Today it's figured out what driver will properly rasterize exotic things like ligatures because we decided that throwing a real CPU in the printer was a mistake.
- bombcar 2y ago96 was still a few years before all the printers natively supported postscript - HPs had their own vector graphics library for example. Many printers in common use were still “one font wonders” and that resulted in lots of fun.
- epcoa 2y agoUnless you were using anything from that tiny obscure Hewlett Packard operation and didn’t want to shell out for a module. HP never promoted Postscript. It was far from universal as an embedded PDL. > that throwing a real CPU in the printer was a mistake. The CPU in any decently modern printer is still many times more powerful than what was in an original LaserWriter (30ppm and up needs power, even if it’s simple transforms and not running wankery). It’s not just about CPU power and modern laser printers still support PDL and vector languages like PCL and PDF (and many have some half assed often buggy PS “compatibility” eg BRScript), the bigger mistake is using general purpose Turing tarpit that is “powerful” rather than a true high level built for purpose PDL. PostScript just isn’t very good and was always a hack. > Send PostScript, done. The other problem of course being that raw PostScript as a target for most applications is not at all elegant and ironically too low level. So even if you wanted postscript, an OS that didn’t provide something more useful to most applications was missing core functionality. The jwz quote about regexes applies just as well.
- wbl 2y agoI have a modern Canon laser printer that does not properly implement ligatures because of obscure driver issues. What I see on the screen is not what is printed.
- epcoa 2y agoText layout is hard and unfortunately drivers and firmware are often buggy (and as printing is lower and lower margin that doesn’t get better). But just throwing a weird language engine in doesn’t actually solve any of those problems.
- wbl 2y agoText layout doesn't need to be done when the source is a PDF. Make printers do the PDF and let Adobe control trademark access via conformity tests and life is good.
- epcoa 2y ago> Text layout doesn't need to be done when the source is a PDF. PDF isn’t entirely a panacea, since it’s complex enough that printing any random PDF isn’t trivial at all, but sure, close enough, but before you were talking about Postscript. > Make printers do the PDF and let Adobe control trademark access via conformity tests and life is good. PDF printers aren’t all that uncommon. So why doesn’t your Canon do this? These aren’t technical issues at all. This is an economic/financial problem as mentioned (doing business with Adobe!). This isn’t about part cost, a CPU 100x more powerful than the one in the LaserWriter is nothing.
- bombcar 2y agoThe biggest errors I’ve found are when the PDF says it’s using FontX or whatever, the printer claims to support the same version, and it’s subtly different. The PDF tool assumes it doesn’t have to send the full font, and the document garbles. Print as image sometimes gets around this.
- 2y ago