Hi Paul,
the only thing you do is to assume EVERYONE in the world accessing
your site uses UTF8. If this would be the case there would never be
a discussion or problem about all this encoding stuff. (Of course
your DB also needs to be Unicode-trimmed, btw.).
But the fact is: You can't be sure what comes in and you may have to
return very different encodings for your outgoing contents.
Of course, almost all relevant browsers will be able to bring your
content up with Unicode/UTF8 encoding so you are save to some point.
If you know you never support, e.g., eastern content you will prefer
to set up your database with the correct ISOxy encoding as it simply
is faster for almost all SQL actions. And then again you have to
deal with AOLserver encodings.
Henry:
The request processor uses ns_adp_parse for the ADP files (I think),
and not "OPEN", and because the code is always single byte stuff,
they run into no problem.
