99 * Test the named character encoding to verify that it converts ASCII |
99 * Test the named character encoding to verify that it converts ASCII |
100 * characters correctly. We have to use an ASCII based encoding, or else |
100 * characters correctly. We have to use an ASCII based encoding, or else |
101 * the NetworkClients will not work correctly in EBCDIC based systems. |
101 * the NetworkClients will not work correctly in EBCDIC based systems. |
102 * However, we cannot just use ASCII or ISO8859_1 universally, because in |
102 * However, we cannot just use ASCII or ISO8859_1 universally, because in |
103 * Asian locales, non-ASCII characters may be embedded in otherwise |
103 * Asian locales, non-ASCII characters may be embedded in otherwise |
104 * ASCII based protocols (eg. HTTP). The specifications (RFC2616, 2398) |
104 * ASCII based protocols (e.g. HTTP). The specifications (RFC2616, 2398) |
105 * are a little ambiguous in this matter. For instance, RFC2398 [part 2.1] |
105 * are a little ambiguous in this matter. For instance, RFC2398 [part 2.1] |
106 * says that the HTTP request URI should be escaped using a defined |
106 * says that the HTTP request URI should be escaped using a defined |
107 * mechanism, but there is no way to specify in the escaped string what |
107 * mechanism, but there is no way to specify in the escaped string what |
108 * the original character set is. It is not correct to assume that |
108 * the original character set is. It is not correct to assume that |
109 * UTF-8 is always used (as in URLs in HTML 4.0). For this reason, |
109 * UTF-8 is always used (as in URLs in HTML 4.0). For this reason, |