> It is a .txt file with ascii. No postscript
> or PCL files or knowledge.
Part of the fun here is that you could be
sending PostScript to your printer without
knowing it.
> We are printing directly to HP and Canon
> printers
Not many details there.
> via stream printing through DCPS and
> Scriptserver usually to port 9100.
I know nothing about "Scriptserver", and not
very much about DCPS, but I believe that DCPS
sends PostScript to a printer. (It certainly
sends PostScript to LasetJet 4MV.)
> Was thinking of having them convert using
> A2PS and then they could insert the
> postscript codes to change the font. Of
> course neither me or the admin in charge of
> the application know postscript.
That would be one way to get the job done.
DCPS should be smart enough to notice that
it's getting PostScript instead of plain
ASCII text, and then not do its own
text-to-PS conversion. (I'd look at the DCPS
manual, but HP's new modern-PDF-only
documentation policy defeats my old XPDF
program, and the disk in my Mac just died.)
A possibly easier method would be to convert
the text to HTML, where it's pretty easy to
fiddle with text size and boldness, and then
find some HTML-to-PS converter. (A Web
browser can do it, but it may be difficult to
get a Web browser to do it in a
non-interactive way, and without adding its
own header and footer noise.)
Many years ago, I actually looked at
PostScript long enough to do something
useful with it, but it's been so long that I
don't remember exactly what it was that I
did. (It's sad, isn't it?) I do remember
spending a lot of time leafing through a fat
book from Adobe. (Probably available in PDF,
now.)
The amazing thing (to me) is how little I
print anything nowadays. I probably haven't
use the LaserJet for over a year. I
sometimes miss the thick piles of tractor-fed
green-bar program listings, but not enough to
make me feed the LaserJet.
