Re: CGIDEV2 doesn't like CCSID 1208?

Scott Klement wrote:

Hi Adam,

I'm not sure what difference it's going to make... When CGIDEV2 reads your template file into memory, it converts it to EBCDIC. When Apache sends it back to the browser, it converts from EBCDIC to (by default) ISO-8859-1 (CCSID 819).

In my case, Apache is not involved (just using wrtHTMLtoSTMF()). However, good to know for future reference.

So it doesn't really matter what your stream file in the IFS is coded as -- it's going to get translated to EBCDIC and then back to 819 before being sent to the browser.

That's what I thought, but I wanted to mention the CCSID of the template file in case I'd missed something. Thank you for confirming.

However, if you want to change CGIDEV2 to work with UTF-8 (or any other IFS CCSID that's either double or mixed-byte) I did post the needed code changes in the following message from Easy400Group's mailing list archives:
http://tech.groups.yahoo.com/group/Easy400Group/message/10335

Thank you.

CGIDEV2 was originally written for pre-V5R1 -- and the IFS didn't support CCSIDs back then, it was codepage based. You can't use multi-byte or mixed-byte encodings with a codepage. (UTF-8 is mixed byte.)

/me lightbulb over head

Duh! I was thinking that codepage and CCSID were synonyms. The earliest release I used was V5R1, and I wasn't doing anything IFS based at the time. Thanks for the correction.