Hi Reed, A quick followup - I tried running reports against a test account with Chinese ads yesterday and noticed that CSV report format is actually encoded in UTF-8. So if your program were UTF-8 aware, then the data wouldn't be mangled when you read it.
Excel does not recognize the UTF-8 csv file format, it expects csv files to be ascii encoded, and hence displays mangled characters when you open the downloaded csv in excel. That's a different issue, and is not due to report contents encoded incorrectly. Cheers, Anash P. Oommen, AdWords API Advisor. On Jan 18, 12:06 pm, AdWords API Advisor <adwordsapiadvi...@google.com> wrote: > Hi Reed, > > I've opened issues with the AdWords team for both the cases you > reported. I'll update you once I hear from them. > > Cheers, > Anash P. Oommen, > AdWords API Advisor. > > On Jan 14, 6:01 pm, Reed <r...@powellgenealogy.com> wrote: > > > > > This problem just gets stranger and stranger. I think I found a > > "solution" - if I specify CSVFOREXCEL as the report format instead of > > CSV, then I get a double-byte file that Excel opens and shows the > > correct Chinese characters. BUT - the file is tab-delimited, not > > comma delimited, despite the format being CSVFOREXCEL. > > > ?? > > -reed -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en
