Subject: [netatalk-admins] Why don't binary encoded prints work?
From: Tom Fitzgerald (tfitz@MIT.EDU)
Date: Mon May 24 1999 - 16:05:34 EDT
This has been driving me nuts....
Are there any explanations on the net of why binary-encoded print jobs,
fed to non-Mac print spoolers, consistently don't work? I've been
taking this as a matter of faith for years, but it's a pain trying to
educate the users about this, and it's irritating that ascii-encoded
jobs are so much larger. (Users here regularly spool 36"x48" postscript
jobs at 100 dpi, you can imagine what an impact a 50% size increase has
on printing time.) To top it off, some applications don't let you
specify ascii encoding at all, and so simply can't print through netatalk.
I assume it has something to do with CR/LF conversions corrupting the
binary data, but I've never caught any data in the process of being
corrupted. Clearly, raw binary from PCs or Unix systems work fine.
Is the corruption something that can be overcome on the server side?
Any enlightenment would be appreciated.
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:16:44 EST