Ok here are more detailed tests that my friend and I went thru today, we used RPM installations for OpenACS:
1. Using psql, insert into and select Big5 (double-byte character encoding for Chinese) data from the database, with both UNICODE and EUI_TW multi-byte database settings..... *all worked*.
2. Simple tcl proc to select the existing Big5 data from the database, thru the OpenACS architecture (browser << aolserver + tcl << pgdriver << postgresql)..... *worked*
3. Simple tcl proc to insert Big5 data into the database, thru the OpenACS architecture (browser >> aolserver + tcl >> pgdriver >> postgresql) and then check data with the same proc from #2 above..... ****FAILED****
Can we safely say that it is the problem of aolserver + tcl now? And if so, is there any solution to this?
