digitalpoint
Mar 4th 2004, 7:08 pm
This is mostly just for informational purposes, but #26 in the Google API FAQ (http://www.google.com/apis/api_faq.html) says they are working on remedying the fact that the API does not return correct results for Chinese, Japanese and Korean keyword queries.
Well, it turns out it's a problem with the client-side, *not* Google's backend. I ended up writing my own SOAP client for the keyword tracker, and after much fiddling with it, I realized that it's just that Google's servers are very specific about how the character set is passed within the HTTP request header. Fixing that fixed the whole problem. Google should buy me a beer.
- Shawn
Well, it turns out it's a problem with the client-side, *not* Google's backend. I ended up writing my own SOAP client for the keyword tracker, and after much fiddling with it, I realized that it's just that Google's servers are very specific about how the character set is passed within the HTTP request header. Fixing that fixed the whole problem. Google should buy me a beer.
- Shawn