Can't search certain characters in GB2312 Build: 0508 Branch OS: Chinese Windows 98 Steps: 1. Using IMAP account (not POP), send yourself a message with the following chars in either subject or body; ”É �U For example, I sent a message with "”É" as a subject. 2. Bring up the Advanced Search and search for a message which contains "”É" in its subject 3. No matched are found. So far, these are the two chars that I encountered. Other single char search worked fine. I did the same thing on POP account. It worked OK.
Those two characters mentioned in Jeesun's report are GBK characters. Same problem occurs to the other GBK characters. I noticed that there is no warning message when I send a gb2312 mail which contains characters that are in GBK range but not in gb2312 range. And search for those GBK specific characters fails no matter the mail is sent in GB2312 or GBK. And I don't see this problem with quick search.
QA Contact: ji → jeesun
Summary: Can't search certain characters in GB2312 → Can't search GBK characters in Advanced Search
Changed the platform to all since I see the problem on linux 05/09 1.0.0 build.
Hardware: PC → All
Same search problem with advanced search for gb18030 characters, like �9ø8�9ø9. The difference is that it does give charset warning message if a GB18030 char is included in gb2312 or gbk mail.
Summary: Can't search GBK characters in Advanced Search → Can't search GBK/GB18030 characters in Advanced Search with an IMAP account
Jeesun, how about the search in AB , would the entries with those chars be found?
Nominating for nsbeta1
Answer to comment#4 -how about the search in AB , would the entries with those chars be found? - AB can find those chars.
cc to taka, does the server support GBK/GB18030?
Status: NEW → ASSIGNED
this problem only with IMAP4 and GB18030. Currently, Enterprise market in China is not our focus, nsbeta1- it.
Keywords: nsbeta1 → nsbeta1-
According to taka, this is a server issue. If the server does not recoginze GB18030 then the search does not work. Invalid, since this is not a client problem.
Status: ASSIGNED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.