![]() (They can be used with the command-line print-tools like lpq, lpr, etc.)Īnd that is why NO RDP client on OSX forwards them! They just forward regular printers. For non-Postscript printers CUPS provides a Postscript converter that translates the Postscript to something the non-Postscript printer understands.įor a RAW printer this conversion to Postscript can't be done, so RAW printers are not offered to OSX GUI applications as valid print-devices. ![]() ![]() On OSX you can create a so-called "RAW" print-queue by using the commandline lpadmin tool or by using the CUPS webinterface at However such RAW printers do not show up as regular printers in OSX, because OSX GUI applications absolutely need a printer to be Postscript. ![]() If the Zebra doesn't use a Zebra LAN interface but another brand you usually need to use "auto" or "text" for the -P parameter. Please note (2): PORT1LF is the normal queue-name used internally by Zebra LAN-interfaces. H (hostname) specifies the ip-address of the printer, -P the queue-name, -l means "file is already formatted, don't touch the content". Please note: -H and -P are case-sensitve !! "-l" is a lowercase L. The customer would have to run something like this on a commandline in Terminal: lpr -H -P PORT1LF -l If the customer printer is a network printer (I seem to recall the GXxxxt models have the regular Zebra LAN interface) you may be able to supply the raw ZPL file to the customer and have the customer send it manually to the printer using the good old lpr command. This is nasty because you don't really have an easy way around that. Your application ignores that and pushes the RAW ZPLII to the Mac anyway, but the Mac was expecting to receive Postscript and hence your error message when it tries to interpret the Postscript file (which is actually no Postscript, but ZPLII). (Windows usually sees it as a "MS ImageSetter device" which is a generic Postscript printer.) So the Remote Desktop APP sees a "postscript" printer on OSX and communicates that to your Windows server. Then converts the postscript output to whatever language the printer needs (ZPLII in your case). OSX internally treats EVERY printer as postscript at the OS level. There is no such thing as a generic text printer on OSX. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |