bump. Anybody using .NET and CSV or TSV having trouble with unicode handling? (seems to work OK with XML, so I am thinking this is a library issue.)
Maybe someone from the .NET team could weigh in? On Sunday, August 19, 2012 8:49:01 AM UTC-4, Crosby (StoneTempleConsulting) wrote: > > following up a bit... > when I download with DownloadFormat as CSV or TSV, i get the same issue. > But when I download as .XML, the characters seem to come down encoded > correctly. > > ... this is looking more like a .net library issue? > FWIW, I'm on v13.3.0 of the .net client library. > > Does anybody know if this issue has been resolved in a more recent version? > I'd like to upgrade, but haven't work through the migration yet - i've got > a fork where I'm working on it (different issue). > > thanks! > > -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en
