 |
|
|
|
| Obviously, only GB18030 character set itself and Unicode character set can contain the GB18030 characters. To support GB18030, application should run in either environment. Here is the environment where the web application run:
- Operation System: Windows 2000 Server.
- WebSphere Application Server: We use WAS 5.0 as a running environment for web application. WAS 5.0 supports both GB18030 and UTF-8 encoding in servlet request and response.
- Data source: We choose DB2 UDB 8.1 as the data source. UDB 8.1 does not provide a native GB18030 database but UTF-8 database to store GB18030 data. We choose six DB2 data types to verify they work well with GB18030: CHARACTER, VARCHAR, LONG VARCHAR, GRAPHIC, VARGRAPHIC, LONG VARGRAPHIC.
- JDBC: We use DB2 JDBC Type 2 driver: COM.ibm.db2.jdbc.app.DB2Driver. We do not verify JDBC Type 4 once more, for we think the GB18030 support in a web application is JDBC Driver independent.
- Browsers: Both Microsoft IE 6.0 and Netscape 7.0 support GB18030 and UTF-8 encoding. In IE, user can choose View > Encoding to select the encoding, while in Netscape, user chooses View > Character Encoding. Also, in the browser’s language setting, Simplified Chinese (zh-cn) should be at the top of the list, and the font should be set to a GB18030 font, such as “SimSun-18030”.
|
|
 Continue to Inserting data
|
|
|
|
| | |
