Code Page

Howard,

The browser should be supplying the code page to the server in the
MIME header, and the server then (optionally) converting the data
to the job CCSID in effect for your application.  If the browser does
not send the MIME header information then the server is assuming
the CCSID specified in the configuration information.  This can be
customized per server instance using options such as CHGHTTPA or
server directives such as DefaultNetCCSID.  The "optionally" I refer
to above is that there are also directives to tell the server what
to (and what not to) convert from the browser code page to the local
job CCSID.

If you are unable to find the correct combination of server configuration
options to meet your needs, then you can also just fall back on doing
code page conversions yourself (using for instance iconv).

Bruce

>
>We have a situation where some folks out of the country send data in
>thru a web application. When the data arrives here it has upper ascii
>characters "mit der umlaut" etc... I believe that the code page would
>help here, but do not know if the sender is responsible or not. Actually
>
>it does not matter if the sender is or is not, we need to convert this
>stuff to our code set. Anyone have any ideas on how to do this?
>

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---