Re:Sysadmin war story: the network ate my font
by 24gttghh on Friday September 15, 2017 @08:20PM
(#15261950)
I should point out that a co-worker tried to convince people we could easily do it with a generated PDF and throw away the damn $500 MICR device but that was swiftly deemed 'impractical'.
Re:Sysadmin war story: the network ate my font
by notgood on Friday September 15, 2017 @07:44PM
(#15261769)
The engineering time dealing with that printer is probably more expensive than just buying a simpler/better one.
Re:Sysadmin war story: the network ate my font
by 24gttghh on Friday September 15, 2017 @08:01PM
(#15261856)
Close. To be fair the printer is supposed to support PCL5, and this is the first time I've witnessed this happen.
Re:Sysadmin war story: the network ate my font
by kevin_thibedeau on Saturday September 16, 2017 @08:06AM
(#15264249)
If this is so mission critical why not get a proper Postscript printer with an onboard filesystem for font storage. It doesn't make much sense to run a business on consumer junk.
And then the printer you are migrating the MICR device to has decided it doesn't understand the PCL in the font file anymore.
This is 2017 and I just dealt with this today.