I'm having a problem using a printer resident font on an HP 8150 LaserJet printer.
There are actually three printer resident fonts that I'm trying to use for a check printing process; a signature font, a secure digits font and the micr line font. I retrieved the PCL font list with their escape codes from the printer. I was able to print all three fonts by hard coding the hex equivalent of the escape codes into a DDS and using the TRNSPY keyword. This was in a SCS data stream.
I then wanted to pull in an overlay that would contain all the static information needed to print on the check. I designed it in Word and printed it on the AFP print driver and then imported it via iSeries Navigator.
Now, in order to use the overlay, I would have to change the printer file from SCS to AFPDS, which led to the TRNSPY keyword to not work and thus not being able to hard code the hex string. So, that led to me reading up about modifying an existing HP Workstation Customization Object. I modified the Workstation Customizing Object to embed the hex strings and associate it with a font id. This worked great as I was able to use the FONT keyword in my DDS and got rid of the TRNSPY keyword. However, I can't for the life of me figure out why the micr font won't print... It's driving me crazy. The only thing that is different is the micr font appears in the "Internal Scalable and Bitmapped Fonts" list and the other fonts (signature and secure digit) appear under the "PJL Resident Fonts" both of which are subsets under the "PCL Font List" I obtained from the printer itself. I don't think it should matter, cause I SUCCESSFULLY was able to print the micr font from the iSeries using hard coded hex strings, why wouldn't it work now like it's working for the other fonts? If you have any idea what I might be doing wrong, I'd really appreciate some assistance.
I am extremely frustrated right now, I would really appreciate any help I can get.
March 26, 2009 2:34 PM
June 20, 2011 2:50 PM