Quote:> > It all depends on what you mean by "handle". :-)
> Ah, good point, Mike. :)
I like to think that I have my moments. Perhaps, not as often as I'd like,
but they do happen from time to time. :-)
Quote:> I'm really trying to find out if ZetaFax
> has native file imaging. If I feed it a file
> with embedded PCL codes (just like I'd
> submit to a laser printer), will the resulting
> fax look like the laser-printed version?
Not wishing to labour a point, (even though you said it was a "good" one),
but it depends on what you mean by "feed". :-)
<FX: Deep breath>
Obviously, I do not know exactly what you have in mind so I cannot give an
absolute answer but I would say that if you have an existing program which
creates a printed page exactly how you want it, then you *should* simply
need to add a few extra lines to the top of the document for the addressing
details and send the resultant output to the ZetaFax printer instead of the
laser you're using at the moment and Robert is your father's brother.
(I think you'll require "embedded addressing" support which comes as part of
the API toolkit IIRC.)
Quote:> If there's no native file imaging in ZetaFax, then I'd totally agree
> with you.
Since my original post, I've taken the liberty of checking with Equisys tech
support and their "official" answer is:
"ASCII, BMP, DCX, EPS bitmaps, Epson FX and LQ Series, GIF, JPEG, PCX, PICT,
Targa, TIFF and 'other' file formats are supported."
When prompted, she couldn't really expand on which "other" file format are
supported, but she did add "any file format may be sent as a fax by printing
from the application that created it.".
Reading between the lines, (and from what I remember), the file formats
listed above can all be "included" in an outgoing fax by simply adding a
"%%FILE (Filename (with path))" at the relevant point. (An outgoing fax can
contain any number of "%%FILE" inclusions.)
If you want to use a file format that isn't listed there, then print it from
the application concerned and use embedded addressing. If your chosen
flavour of MV supports ODBC then that might be the way to go anyway as you
can do everything from within the "application".
Quote:> The plot thickens...
Well, I suppose that's why clients pay folks like us to solve their problems
for them. ;o)
Quote:> Mike, thanks very much for your comments.
No problem. Glad I was able to help, (assuming I have helped?).
Quote:> If and when I get the time to play with it,
> I'll do exactly as you suggested.
If and when you get the time, if you feel I can help further, please do not
hesitate to ask either in CDP or directly via e-mail.
Quote:> The only problem
> is that my inbox is about a mile high...
You can swap it for mine if you like. No clues as to how high mine is
before you make your decision though... ;o)