× 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.



Thank you Scott and Vern!

Actually, after I pressed Send, I thought of another way and also that
this is really only going to a PRTF to make a PDF which gets emailed.

I just reformatted the printout a bit and hopefully that'll do the trick.

Thank you,

Doug





From: "VERNON HAMBERG Owner" <vhamberg@xxxxxxxxxxxxxxx>
To: rpg400-l@xxxxxxxxxxxxxxxxxx
Cc: denglander@xxxxxxxxxxxxxxx, rpg400-l@xxxxxxxxxxxxxxxxxx
Date: 12/19/2023 03:41 PM
Subject: [TAKE CAUTION] Re: PRTF and hex codes



I remember the use of "transparency" at a previous (over 25 years ago, I
think) employer - a title insurance company - and they needed different
fonts and managed layout when printing to HP printers. I also remember it
seemed to be almost a full-time position. I also don't remember the
details and will not spend time looking.

Cheers
Vern

On Tue, 19 Dec, 2023 at 2:41 PM, Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>
wrote:

To: rpg programming on ibm i
Cc: DEnglander@xxxxxxxxxxxxxxx
Doug,

When you "add hex characters" (i.e. 5250 color attribute codes) into
your text for a display file, you are making a bet... the bet is that
this application will always use a 5250 type terminal for it's display.
If it ever gets run on a different display device (and there isn't some
software that translates the 5250 codes to the other technology) then it
won't work anymore.

That may be a safe bet?

Now consider the same one with a PRTF. You are betting that you will
always use the same printer. Or at least a compatible one. Is that a
safe bet?

Personally, I'd say no. Printers change often, and they wear out and
are replaced with different types. Hard-coding a printer escape
sequence will likely mean your program need to be rewritten as soon as
the printer is changed. I wouldn't make that bet, myself.

If you want to make it, however... there is a feature called
"transparency" that can be used. With this feature, you can insert a
sequence of bytes that says "the next X number of characters are to be
treated as transparent, and not converted" and then you can use that to
insert the printer's escape code to enable/disable bold.

I won't take the time to look up the details, because I think it'd be a
bad idea to do it, so I don't want to invest the time.


On 12/19/23 1:47 PM, DEnglander--- via RPG400-L wrote:
I know there is a way for RPG to add hex characters to a field to allow
certain words within a field to be in color, when displaying on a 5250
session.

Does anyone know if there is a similar way to perform that function with
a
PRTF that is defined as *SCS? I am specifically looking to have one
"word"
[really a balance due] be bolded on the printout. Currently, the
HIGHLIGHT
keyword is used, but because of the size of the field, there is a lot of
white space surrounding the number in its accompanying sentence. I was
thinking of composing a string in the program, not use HIGHLIGHT, and
then
have RPG insert the Hex character for HIGHLIGHT [on] + HIGHLIGHT [off].
Is
that possible?

Thank you,

Doug



"CONFIDENTIALITY NOTICE: This e-mail transmission (and/or the
attachments accompanying it) contain confidential information belonging to
the sender. The information is intended only for the use of the intended
recipient. If you are not the intended recipient, you are hereby notified
that any disclosure, copying, distribution or the taking of any action in
reliance on the contents of the information is strictly prohibited. Any
unauthorized interception of this transmission is illegal under the law.
If you have received this transmission in error, please promptly notify
the sender by reply e-mail, and then destroy all copies of the
transmission."

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.