× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



It sounds as though you aren't getting a good match between the fonts on
your overlay and the fonts in the printer. Normally you get good
substitutions, but don't use the 13.3 CPI fonts in your overlay. Those are
a proprietary font copyrighted by IBM, and unless you are printing to an
IBM/Lexmark printer you will not get a good substitution. Check your
message queues, and the QSYSOPR message queue for font substitution
messages. Track those down and change the requested fonts to something
that the printer knows. Do you have the AFP Font Collection installed?
That should provide the fonts you need.

Good luck,

Steve

Steven Morrison
Fidelity Express
903-885-1283 ext. 479



"tim" <tim2006@xxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
04/17/2007 07:44 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
<midrange-l@xxxxxxxxxxxx>
cc

Subject
RE: MIDRANGE-L Digest, Vol 6, Issue 795






Steven,

I am creating the overlays with my IBM AFP printer driver. I defined my
printer file as DEVTYPE(*AFPDS), upload the overlay and print the
document.

The reason I am asking about uploading a PC font to the iseries is that
when
I view my spooled file via AFP viewer in iSeries Navigator, it looks
great.
When I print it to my hp4050TN network printer, it looks terrible. I
realize
there is some translation happening. I was thinking that uploading the
same
fonts that are resident on the printer to the iseries will solve the
problem. Is that a correct assumption?

Tim


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.