|
> Actually for the above sequence of characters (8U in the > O-specifications, according to references and manuals, the desired > result is the font in the print out should be " Roman 8". When we try > generating the reports by executing these programs, we have these > special characters appearing in the hard copy (Print out of the spool). I had somewhat of a similar problem when changing a printer from twin ax to ethernet. After making the change all of the reports that used to print on it now printed in a different font and one report in particular did not print in duplex anymore. I looked at the program that used to print in duplex and found the following values ¬D1 and ¬D0 hardcoded into the O specs. Along with &%1B266C33303055&% &%1B266C30303055&% &%1B45&% There was zero documentation as to what those values meant. After doing my best Sherlock Holmes impression I found that the ¬D1 and ¬D0 were for duplexing and the other values were for setting the font type and point size. These strings or commands were meant for the IO PrintBox that was used when the printer was connected via Twin Ax. My understanding of the PrintBox is that it is a box that contains a printer interface card. It can be tailored to work with various printers. In my case an HP 8100. What I did to fix this was take out the print command and used an OVRPPRTF command to handle the duplexing and font settings. I was able to get the report to duplex with the correct font size but I was never able to get the exact font type. I couldn't figure out what &%1B266C33303055&% and &%1B266C30303055&% translated to. So to make a long story short can you comment out the PCL and try to use a print file override?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.