1. Bytes and Unicode Java kernels are Unicode, even Class files are also, but many media, including file / streams save ways to use word current. Therefore, Java is to transform these byte streams. Char is Unicode, and Byte is byte. The functions of Byte / Char in Java are in the middle of Sun.IO. The BytetocharConverter class is scheduled, which can be used to tell you, you use the Convertor. Two of these very commonly used static functions are public static bytetocharconvert (); public static bytetocharconverter getConverter (String eNCoding); if you do not specify Converter, the system will automatically use the current Encoding, GB platform with GBK, EN platform 8859_1. BYTE -> Char: "You" GB code is: 0xc4e3, Unicode is 0x4f60 string encoding = "gb2312"; Byte B [] = {(byte) '/ u00c4', (byte) '/ u00E3'}; bytetocharconverter Converter = bytetocharconverter.getConverter (Encoding); char c [] = converter.convertall (b); for (int i = 0; i Char -> byte: string encoding = "GB2312"; char C [] = {'/ u4f60'}; chartobyteconverter converter = chartobyteconverter.getConverter (Encoding); Byte B [] = Converter.convertall (c); for (int); for i = 0; i String.length () is actually the length of the char array, and if you use different codes, it is likely to be scattered, resulting in scattering and garbled. For example: String encoding = ""; byte [] b = {(byte) '/ u00c4', (byte) '/ u00E3'}; string str = new string (b, eNCoding); if encoding = 8859_1, there will be two One word, but eNCoding = GB2312 is only one word. This problem occurs frequently in processing paging. 4. Reader, Writer / InputStream, OutputStreamReader and Writer core are CHAR, INPUTSTREAM, and OUTPUTSTREAM cores are BYTE. But the main purpose of Reader and Writer is to read Char read / write InputStream / OutputStream. For example: file test.txt has only one "you" word, 0xc4, 0xE3String Encoding = "gb2312"; inputStreamReader reader = new inputStreamReader (New FileInputStream ("text.txt"), encoding; char c [] = new char [10 INT length = reader.read (c); for (int i = 0; i But we tend to ignore this parameter, so this often has a cross-platform problem: sample code compiles on the Chinese platform, generates the zhclass sample code compiled on the English platform, outputs Enclass (1). ENCLASS executive on Chinese platform OK, but not on the English platform (2). Enclass executes OK on the English platform, but not on the Chinese platform: (1). After compiling on the Chinese platform, in fact, STR is running with the state of the state [] is 0x4f60 In the Chinese platform, the default code of FileWriter is GB2312, so the ChartobyteConverter automatically uses the CONVERTER calling GB2312 to convert the STR into the fileOutputStream, so 0xC4, 0XE3 is put into the file. But if it is in the English platform, the default value of Chartobyteconvert is 8859_1. FileWriter will automatically call 8859_1 to transform STR, but he can't explain, so he will output "?" (2). After compiling on English platform, in fact STR CHAR [] is 0x00c4 0x00E3 in the running state, running on the Chinese platform, there is no way to identify, so it will appear; on the English platform, 0x00c4 -> 0xc4, 0x00e3-> 0xE3, therefore 0xc4, 0xe3 is put into File. 6. Other reasons: <% @ page contenttype = "text / html; charset = GBK"%> Set the display code of the browser, if the result of Response is UTF8 encoding, the display will be garbled, but garbled and the above reasons are still different . 7. Places where you have encoded:? From the database to Java programs Byte -> char? From the Java program to the database char -> byte? From the file to the Java program Byte -> char? To the file char -> BYTE? From the Java program to the page Display char -> byte? Submit data from page form to Java programs Byte -> char? From the Java program Byte -> char? CHAR -> Byte Xie Zhi Gang Workaround: I use the method of configuring the filter to solve Chinese garbled:
