That is correct -- ns_getform should always be used instead of ns_conn form. ACS 4 has this done consistently. In my patches for i18n we decided to
make ns_getform be the place that you get to declare what encoding
the posted data was in. The implementation of ns_getform takes
an optional encoding arg, and defaults to the site wide default set
in your config file ("urlcharset"). You even get a chance
to call ns_getform again with a different encoding, in case you
guessed wrong for some reason.
Ideally, for Japanese, we need to link
in a heuristic routine into aolserver to guess the charset, in case it is one of
the several that are in use commonly (SJIS, EUC, ISO-2022). Other asian
languages may need this feature as well, if there are several
common encodings in wide use.
