Forum OpenACS Q&A: Response to Internationalization of OpenACS 4.5

Collapse
Posted by Henry Minsky on
I have built several sites that work in Japanese using OpenACS  (v 3 and 4)
and Postgres 7.1 and 7.2.

The info in the above discussion is on the right track.

I have posted some messages before with copies of
the tcl init file needed to set the default
character set and MIME types.

I will try to collect that stuff up on a single web page
that can go someplace easy to find (like on openacs.org).

See
https://openacs.org/bboard/q-and-a-fetch-msg.tcl?msg_id=0002Uv

Example config file (acs 3)
http://www.ai.mit.edu/people/hqm/openacs/acs3-pg.tcl

Kana conversion routines (half width to full width)
https://openacs.org/bboard/q-and-a-fetch-msg.tcl?msg_id=0002T4

There may be some issues with .adp pages -- the issue was that
AOLserver's adp parser would assume the .adp source file
was encoded as UTF8. The workaround was to modify ACS's
adp parsing code to explicitly load the .adp file source
using a specific encoding (such as Shift JIS) based on the
defined MIME type for .adp files, and then pass the resulting
string to AOLserver's adp parser using the -string option.

The acs-lang package contains a file with a set of patches which
tweak the request processor. I am not sure if those patches
are now merged in with the ACS acs-tcl core procedures, or if it
is still necessary to apply them manually when installing the
acs-lang package.