On 2020-06-26 13:55, Greg Troxel wrote:
Johnny Billquist <bqt%update.uu.se@localhost> writes:Apart from that, I guess it's going to be possibly reading the manufacturers documentation, and if you are unlucky, that printer talks some proprietary protocol, and they provide a Windows driver for you. (Good luck getting such a Windows driver work on any Unix-like system...)All true, but others have gone before. Search for how cups deals. I know you say you don't want to install it, but this is where people have made lots of things work.
Since I don't even have that printer, I obviously don't need this. :-)However, with a quick cursory glance at the printer documentation, it smells like this printer is indeed using some proprietary protocol, and they provide a driver for Windows and Mac. The Windows driver can accept postscript, but obviously the printer itself have no clue about postscript. It certainly looks like it also do not talk PCL. So it's some Brothers proprietary protocol.
Maybe some people have created a driver in CUPS for it, which could be a solution. But without CUPS, I think this is a lost cause.
(Personally I have a printer that do talk PCL, and I can print a plain ASCII file by just sending it to port 9100 on my printer, so I'm all good... :-) )
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt%softjar.se@localhost || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol