I'm up to my ears in Unicode development for AOLserver/ACS/Oracle. If you
have questions, particularly about Japanese, ask me. We have a couple of projects running in Japan which support Japanese charsets for
ACS 3.4.5 or later.
I've got a small patch to AOLserver 3.1 which makes it possible to handle user input in non-ISO-8859-1 charsets. There are
some touchy areas related to when charset encoding conversion gets
performed on user-posted data , and how this interacts with the ACS request processor. I'm working on the i18n for ACS 4 now, so this stuff will work more cleanly in that framework.
I have no idea how Postgres deals with Unicode, but I can help debug
problems with AOLserver. Rob Mayoff wrote the main modifications to
AOLserver to allow it to perform encoding conversions when sending
pages, but there is some extra work that needs to be done in ACS to allow it to load tcl/html/adp files which are in non latin-1 encodings.
You can start by looking at http://imode.arsdigita.com/i18n for some
notes. That happens to be one of my development servers as well, so it may be
out of commission from time to time.
