ASCII Extended

P

PMiddleton

New Member
All,

OE11.2 / Windows 2008

I have the need to print some ASCII Extended characters (specifically Heart, Diamond, Club & Spade) but I can't seem to find the right solution. Is it possible to print these characters?

Here's the only chart I could find but when I try to use CHAR(&#9824) which is a black spade, I can't even get past the syntax.

Any help would be appreciated.

Patrick
 
9824 (2660 hex) isn't ASCII. It is the Unicode code point for "black spade suit". So you will need to use a Unicode code page in your session. What are your -cp* settings?
 
My customer pf file looks like this:

-H DB # host-name
-S somedbservice # service name or port number (4100)
-N TCP # network protocol
-db somedb # physical database name
-pf ..\standard\standard.pf # standard parmeter file

the -pf that is referenced in the customer pf is:
-ld somedb # logical-dbname
-Bt 400 # temp-table-buffers
-mmax 12288 # max-r-code-memory
-T c:\some\temp # temp-file-directory
-TB 24 # sort-block-size
-TM 16 # merge-buffer-count
-yy 1930 # year-offset
-s 1024 # stack
-nb 175 # nested blocks
-rand 2 # a more random number generator
 
Fine, but I asked what is in startup.pf in the OpenEdge installation directory. It should contain settings for -cpstream and -cpinternal.
 
#International component. The International component provides
#these directories and files.
#
-cpinternal ISO8859-1
-cpstream ISO8859-1
-cpcoll Basic
-cpcase Basic
-d mdy
-numsep 44
-numdec 46
 
So the answer is: if you aren't specifying -cp* parameters anywhere else, your clients are using ISO8859-1. Note that you don't have to change this default; you can specify a different code page in the OUTPUT TO statement when you set up your stream, using CONVERT TARGET <code page>. You may have to check that there exists a translation between the source and target code pages.
 
The startup.pf in the Progress installation directory which is created during the installation according to what was entered is used by ALL Progress processes automatically. Therefore, as Rob already mentioned, theses settings are effective unless specified otherwise in an application specific paramter file or on the command line - where the last occurance of the specificiation will win.

Furthermore, Progress will automatically convert between code pages as long as conversion rules are available in the convmap.cp file ( located in the installation directory ). AFAIK, out-of-the-box it contains only conversion between code pages that share the same character set. Obviously a loss-less conversion is only possible when the code pages share the same character set. Nevertheless if there are no conversion rules in the convmap.cp then you need to roll your own.

In your case, iso8859-1 and 437 are not compatible because they do not share the same character set ( while ibm850 and iso8859-1 do ). But since 437 ( http://en.wikipedia.org/wiki/Code_page_437 ) and ibm850 are not that different it might be easy for you to create your own based on the conversion between iso8859-1 and ibm850 that is already in the convmap.cp.

Heavy Regards, RealHeavyDude.
 
You must log in or register to reply here.
Back
Top