![]() |
Lee Howard typed (on Tue, Jan 22, 2008 at 05:09:13PM -0800): > Second (the more significant issue), it appears the there is no sure-fire > way to identify a PCL file. You can see from your system's "magic" file > (often /usr/share/magic) that PCL file detection is a bit of a > best-guess/probability approach... and it's further-muddied by HP's PJL > wrappers around both PCL and non-PCL (usually Postscript) data and the > likelihood that users will want to process PJL-PCL files as if they were > PCL (because GhostPDL seems to usually support that). So we need to take a > look at how to type the PCL files you'll be sending, at least. That typing > information will need to be added to typerules (for the client-side) as > well as hfaxd/FileSystem.c++ (for the server-side). Once we can reliably > type the PCL files that you'll be sending then this issue should not impact > you any longer. (I am told that the <ESC>E<ESC> is the most-reliable way > to detect non-PJL PCL data, and this typing detection is *not* present in > 5.2.1.) <ESC>E (0x1b45) is the PCL command for resetting a printer to its defaults. Another <ESC> *may* follow to introduce some other PCL instruction(s), but an <ESC> by itself signifies nothing and I can't imagine it ever occuring. -- JP ____________________ HylaFAX(tm) Users Mailing List _______________________ To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*