Quote:
|
Originally Posted by Laurens
I did look into this and came to the conclusion that it cannot be fixed because Big5 is a variable-length encoding. The PDB format allows only for a zero-terminated string of 8-bit characters. You cannot fit a variable-length encoding into this.
In short: this cannot be fixed. You should use characters in the Windows-1252 range only.
|
Hi Laurens:
If the DB name does not allow Big5 encoding, how can I change the DB name in plucker to Chinese correctly? The problem is werid.
And, as I know Big5 is a fixed-length encoding. Every Chinese characters composed by two bytes. So, what do you mean "varialbe-length" encoding? I am a little bit confused here ...
I just guess, in Microsoft Traditional Chinese Windows XP/2000, use "big5" as default locale. When sunrise running, sunrise will also convert the "document name" again ....
For example:
"XXYY" is the document name, and is encoded by big5. My channel config as following:
Input: UTF-8 (or others)
OutPut: Big5
So, when sunrise build the pdb file, it will convert the "XXYY" from utf-8 to big5 again and set it to document name..... that's why the document name is "??"
And actaully "XXYY"'s encoding here is big5, not utf-8.
Mark