User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7b) Gecko/20040331 Camino/0.7+ Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7b) Gecko/20040331 Camino/0.7+ http://www.mozilla.org/products/camino/features/searchCustomization.html Encoding search-string to multibyte encoding (Shift-JIS, EUC-JP, UTF-8, etc) is necessary to search with various language. at present, Camino always encode search-string to UTF-8 and send it. But almost search services by CGI require same encoding of search page. If charset of search page = "EUC-JP" , we should encode search-string to "EUC-JP". we should change encoding each search site for Customizing Search Engines. Reproducible: Always Steps to Reproduce:
Created attachment 145254 [details] simple patch with sample of SearchURLList.plist. Change SearchURLList.plist: Set NSDictionary to encoding Number and URL. encoding Number is enum kCFStringEncoding at Core foundation.
I'm using Google Japan as default ToolBar Search with SearchURLList.plist settings as below; <key>Google</key> <string>http://www.google.co.jp/search?q=%s&hl=ja&ie=UTF-8&oe=SHIFT_JIS&lr=lang_ja&num=100</string> And it seems for me there are no problems. Are there any differences of results between encoding UTF-8 and encoding SHIFT_JIS?
I'm sorry, I misunderstood. Yahoo Japan can't find out the corresponding strings of UTF-8.
This bug is not RESOLVED and not INVALID. Please read my first comment again. Camino always encode search-string to escaped UTF-8. Fortunately Google have option to enable escaped UTF-8 ( "ie=UTF-8" ), but almost search engine don't have such option and require various charset. ( Alphabet are assigned same block in most charset and trouble has not happenned. ) If we use only Google, no problem. but when we customize search engine, we should change charset be suitable for each search engine.