×
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.
On 13-Aug-2015 08:04 -0600, Jeff Young wrote:
I have been asked by a friend if there is a way the Trademark
Symbol can be stored in a database file and then printed on a
document.
The code point 0xAF in CCSID 37 is the character identifier SM530000
described as the "Registered Trademark Symbol" with the
[apostrophe-delimited] glyph '®' rather than the [apostrophe-delimited]
glyph '' [which unlike the earlier RTS, that TM symbol does not appear
for me properly as the expected glyph after pasting the 0xC299 character
into this UTF8 message]
From what little I know, I believe that if he wants it in a database
file, he can create the table with SQL and add a BLOB field.
Per above, a properly CCSID-tagged column can have the EBCDIC
Registered Trademark Symbol *character* entered just as any other
visible glyph. Of course the chosen font must properly represent that
character\code-point as well.
How would that be loaded / retrieved and sent to a printer via an
RPGLE program?
I thought about creating a PF, but that would first require getting
the symbol in the spool file first.
Any suggestions will be appreciated.
Perhaps instead the stated intent, is to print their particular
trademarked _logo_ for which they have an image file such as a GIF, TIF,
PNG, or JPG binary?
As an image, presumably the typical method used is to print that as
an Overlay resource object (*OVL). The binary image data can be
created\retrieved elsewhere and /imported/ to the member of a Physical
File (PF) or Stream File (STMF) [the latter, at least indirectly] from
which the overlay is created\compiled using the Create Overlay (CRTOVL)
command.
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.